Keep track of entries that are read-only or r/w in separate caches. This is an optimization that avoids writing back all accessed entries back to the database on a flush.
Also makes the way clear for future optimizations such as putting a fixed limit on the size of the read cache, by using a different data structure for the read and write cache.
I've tested this with a full reindex on testnet and mainnet, as well as checkblocks. I wonder how it will fare under the pulltester.
Make intention more clear:
- Call ModifyCoins if you intend to change the coins
- Call GetCoins to get a const reference to the coins
This can be used for dirty tracking later on.
Keep track of entries that are read-only or r/w in separate
caches. This is an optimization that avoids writing back all
accessed entries back to the database on a flush.
Also makes the way clear for future optimizations such as putting a
fixed limit on the size of the read cache.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/p4684_9fd43c3334c201b1c3741ad6b5ef1b546bbe1c1c/ for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
Closing for now, still needs some work