We're seeing multiple reports of bitcoind / bitcoin-qt running out of virtual memory on 32 bit systems. It may actually be nearly impossible now to sync the chain in an x86 system or at least require several crashes and restarts.
Bitcoin is running 32 bit systems out of virtual memory #3324
issue gmaxwell opened this issue on November 28, 2013-
gmaxwell commented at 8:19 AM on November 28, 2013: contributor
-
laanwj commented at 8:47 AM on November 28, 2013: member
Could be another effect of leveldb's liberal use of mmap.
-
ghost commented at 12:58 AM on November 29, 2013: none
Yep, I can confirm that. A full sync from block 1 took something ridiculous like 16GB of RAM on my bigger server, and to get to sync on a smaller 32bit VPS I had to use a kludgy workaround. Got there in the end, but it's not optimal by any stretch of the imagination.
while true; do bitcoind; doneIs there a reason a full sync takes so much more RAM than just running it normally?
-
laanwj commented at 8:03 AM on May 4, 2014: member
Anecdotally, this appears to be fixed with current master. I started syncing on a 32-bit 4-core ARM box yesterday - from the network, not from a bootstrap, and I'm now up to block 220888 without any abnormal memory usage.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 9138 debian 20 0 578000 390180 1704 S 6.0 21.6 131:51.95 bitcoind - laanwj closed this on May 6, 2014
- Bushstar referenced this in commit e3db956835 on Apr 8, 2020
- MarcoFalke locked this on Sep 8, 2021
