top - 12:21:26 up 1 day, 16:16, 2 users, load average: 3.62, 3.34, 2.89 Tasks: 181 total, 2 running, 179 sleeping, 0 stopped, 0 zombie Cpu(s): 8.0%us, 3.9%sy, 5.7%ni, 16.9%id, 64.6%wa, 0.2%hi, 0.7%si, 0.0%st Mem: 3504896k total, 3400116k used, 104780k free, 62184k buffers Swap: 4050936k total, 296k used, 4050640k free, 2452164k cached Apparently I have 3.5GB ram (really 4gb but it's a 32 bit system) .. I thought it was only 2gb I do run an encrypted filesystem. It's not normally a problem but I guess for bitcoin it is. On 26 January 2013 12:06, Daniel Lawson <daniel(a)meta.net.nz> wrote:
Hey Bruce
LA of 2.5 but CPU under 10% suggests that you're hitting IO limits. What's the %sys or %wa in top?
I'm not familiar with bitcoin, but you said you had 4.5GB of blockchain. If this means you've got 4.5GB of data on disk, and bitcoin is doing a lot of random accesses to it, it will definitely cause this kind of loading.
If you had loads of spare ram you could try moving your blockchain to a ramdisk during the verify, then moving it back once you're done. Alternatively, if you had lots of spare ram, everything might end up fitting nicely in the fs cache, which would also improve random access. Otherwise you're looking at improving your disk IO system, which probably means an SSD.
So just for a test I'm running it again now. I checked and there isn't even the option of CPU mining any more.
My load average has jumped to 2.5, it's normally around 0.1
CPU and memory used by bitcoin seem quite reasonable (both under 10%)
At the moment other programs are behaving but I have bursts where everything gets painfully slow. When I type, it takes five or ten seconds for the words to appear. Firefox keeps going grey. This ONLY happens while bitcoin is running, if I stop it everything goes back to normal.
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug