My problem is this. The recommended advice in order for geth to run a faster initial sync is to use the option --fast
plus a non-default value for the option --cache
. The option --cache
appears to be necessary if you want the fast sync to progress beyond a few percent of the total block sync. For example, a "mere" value of --cache=512
allows geth to fast sync about half of the now over a million ethereum blocks before going down to regular sync, while --cache=768
leads to a fast sync of 700,000 blocks, suggesting a rough ratio of 1 MB RAM per fast sync'd block.
As regular sync is superslow, I'd like the fast sync to progress past the million-block mark. Unfortunately, a value of --cache=1024
leads to an out-of-memory crash. Is there a way to do a fast initial sync without geth consuming gobs of memory?
--minerthreads
, which is obviously related to mining rather than syncing?cache
is the way to go i guess but i see some improvement when i adjust thepeers
please try that too.