I'm finished for this time. My host 103.243.173.214:22556 has 32 maxconnections, a response time (ping) far lower than 1 second, and uses one complete core of the cpu. I will let it untouched this way. From 29 active connections only 5 are current, the remaining has to catch up. This perhaps explains the high cpu load. My system uses a nvme ssd, this is no bottleneck, waiting time for drive access is very low.
hmm usually high cpu load is during block downloading/syncing/verifying transactions, but you are also only using one cpu (4 cores i assume?). If you have the available memory, set your `dbcache=2000` in the dogecoin.conf file. this significantly helps with syncing. and reduces usage of the storage drive, keeping more data in ram.
I have configured dbcache=2048 for all testing now. Even with only 15 maxconnections I have a full load on one core:
# output of top(1)
top - 06:00:14 up 48 days, 13:46, 5 users, load average: 2.27, 2.40, 2.34
Tasks: 252 total, 1 running, 251 sleeping, 0 stopped, 0 zombie
%Cpu(s): 9.1 us, 1.7 sy, 6.7 ni, 78.5 id, 0.4 wa, 0.0 hi, 3.7 si, 0.0 st
MiB Mem : 64225.1 total, 446.5 free, 20889.6 used, 42889.0 buff/cache
MiB Swap: 17360.0 total, 12809.9 free, 4550.1 used. 43043.0 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4164700 doge 20 0 2666100 1.2g 132444 S 98.4 1.9 11:48.79 dogecoind
I have a 6 core 12 thread host. I don't want more cpu usage by one wallet daemon, so this is ok for me, more load is unwanted.
My daemon mostly is some blocks behind the current block. The connected hosts are lagging too. My last block is 3589562, the current one from blockchair is 3589563. I'm nearly current, but the load stays near 100%.
$ ./dogecoin-cli getpeerinfo | grep startingheight
"startingheight": 3589535,
"startingheight": 4688,
"startingheight": 13904,
"startingheight": 15676,
"startingheight": 3589458,
"startingheight": 536920,
"startingheight": 3589489,
"startingheight": 3589509,
"startingheight": 3589550,
"startingheight": 3589407,
"startingheight": 28951,
"startingheight": 4552,
I have a 64 GByte host, and only 1/3 of the memory is used, the remaining is drive cache.
Can this info explain the high load? totalbytessent is incredible high in comparison to totalbytesrecv. And the sent counter rises quickly, after a few minutes it's 1 GByte more.
$ ./dogecoin-cli getnettotals
{
"totalbytesrecv": 8300980,
"totalbytessent": 4952289892,
"timemillis": 1612177939714,
"uploadtarget": {
"timeframe": 86400,
"target": 0,
"target_reached": false,
"serve_historical_blocks": true,
"bytes_left_in_cycle": 0,
"time_left_in_cycle": 0
}
}
My host is ubuntu 20.04.1 LTS. The wallet comes from
https://github.com/dogecoin/dogecoin/releases, file is dogecoin-1.14.2-x86_64-linux-gnu.tar.gz, md5sum is ecc01479161d3c872f0b725f184c8983.