New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closes #2793 to improve sync performance by increasing default value of dbcache. #2873
Conversation
3371f6a
to
7113674
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General utACK, but see comment.
Notable changes | ||
=============== | ||
|
||
UTXO memory accounting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put these in doc/release-notes.md
, which gets inserted into the correct release notes file at release time. This also means you can just cherry-pick upstream commits directly, and their release notes will go into the correct place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, done.
7113674
to
1f2f9e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK after doc comment is addressed.
doc/release-notes.md
Outdated
UTXO memory accounting | ||
---------------------- | ||
|
||
The default -dbcache has also been changed in this release to 450MiB. Users can set -dbcache to a higher value (e.g. to keep the UTXO more fully cached in memory). Users on low-memory systems (such as systems with 1GB or less) should consider specifying a lower value for this parameter. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking: has been changed
(non-blocking because I expect other changes will be added that can go before this, to make it grammatically correct).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
doc/reducing-memory-usage.md
Outdated
|
||
The size of some in-memory caches can be reduced. As caches trade off memory usage for performance, usually reducing these have a negative effect on performance. | ||
|
||
- `-dbcache=<n>` - the UTXO database cache size, this defaults to `450` (`100` before 1.0.15). The unit is MiB (1024) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The (1024)
seems like a typo. Maybe expand to (where 1 GiB = 1024 MiB)
or something similar?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
doc/reducing-memory-usage.md
Outdated
The size of some in-memory caches can be reduced. As caches trade off memory usage for performance, usually reducing these have a negative effect on performance. | ||
|
||
- `-dbcache=<n>` - the UTXO database cache size, this defaults to `450` (`100` before 1.0.15). The unit is MiB (1024) | ||
- The minimum value for `-dbcache` is 4. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Document max?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Depends on the platform, so won't document here. Note that zcashd --help
already displays the max amount: Set database cache size in megabytes (4 to 16384, default: 450)
ACK. @zkbot try |
Closes #2793 to improve sync performance by increasing default value of dbcache.
☀️ Test successful - pr-try |
Adapted from documentation 'Reducing bitcoind memory usage' by @laanwj https://gist.github.com/laanwj/efe29c7661ce9b6620a7
1f2f9e8
to
92adc51
Compare
@str4d updated documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK. Merge when ready 😄
doc/release-notes.md
Outdated
UTXO memory accounting | ||
---------------------- | ||
|
||
The default -dbcache has been changed in this release to 450MiB. Users can set -dbcache to a higher value (e.g. to keep the UTXO more fully cached in memory). Users on low-memory systems (such as systems with 1GB or less) should consider specifying a lower value for this parameter. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking: "to keep the UTXO set"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Adapted from upstream release notes here: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.14.1.md#utxo-memory-accounting
92adc51
to
d2b77b7
Compare
@zkbot r+ |
📌 Commit d2b77b7 has been approved by |
Closes #2793 to improve sync performance by increasing default value of dbcache.
Update version string Pull in select 1.0.15 Zcash fixes: read hashReserved from disk zcash#2931 improve sync performance by increasing default value of dbcache. zcash#2873 z_importviewingkey fix from leto/zero/pull/1 Update README.md throughout, particularly the addnode addresses, plus add a sample zero.conf to ./contrib
No description provided.