You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was noticed that setting the values could possibly overwrite the other corresponding config parameter.
dirty_background_bytes is the counterpart of dirty_background_ratio. Only one of them may be specified at a time. When one sysctl is written it is immediately taken into account to evaluate the dirty memory limits and the other appears as 0 when read.
Will continue to review and possibly test modifications and file a PR for a correction.
The text was updated successfully, but these errors were encountered:
Basho-JIRA
changed the title
Improvement on the I/O section of the Improving Performance document
Improvement on the I/O section of the Improving Performance document [JIRA: DOC-774]
Dec 22, 2016
Good catch with the wording, it is definitely the case that either ratio, or bytes should be set for dirty_ and dirty_background_ settings. Those settings are a starting point for further benchmarking and performance analysis (for 16GB machines), and either the dirty_ratio/dirty_background_ratio or dirty_bytes/dirty_background bytes should be applied depending on how the user wishes to apply them.
http://docs.basho.com/riak/kv/2.1.4/using/performance/#optional-i-o-settings cites that
It was noticed that setting the values could possibly overwrite the other corresponding config parameter.
https://www.kernel.org/doc/Documentation/sysctl/vm.txt
Will continue to review and possibly test modifications and file a PR for a correction.
The text was updated successfully, but these errors were encountered: