Pages:
Author

Topic: Pruned mode syncing doesn't cache file writes? - page 3. (Read 1460 times)

member
Activity: 301
Merit: 74
dbcache was set to 3000. I don't think I saw the process use anywhere close to that much memory, but I'll look more closely next time.

Is dbcache only for the UTXO set? Is it for reads or writes?




staff
Activity: 3458
Merit: 6793
Just writing some code
Increase the size of the dbcache by starting Bitcoin Core with the -dbcache= option or adding dbcache= to your bitcoin.conf file where is the amount of RAM in MB that you want to dedicate to the database cache. Increasing this will reduce the amount of disk IO that is done as the database will be flushed less frequently. A dbcache of ~6000 should allow the entire database cache to be held in memory so only on flush is required.
member
Activity: 301
Merit: 74
I have Bitcoin Core in prune mode.
I've launched it after one offline day, and syncing really grinds the HDD and barely progresses. It's doing something like 1 block per minute.

In the chainstate directory only 250MB of files were touched, so writes are easily cacheable.
Is there a way to get write caching?

Pages:
Jump to: