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
Increase default arc_c_min #6659
Conversation
Increase the default arc_c_min value to which whichever is larger, either 32M or 1/32 of total system memory. This is advantageous for systems with more than 1G of memory where performance issues may occur when the ARC is allowed to collapse below a minimum size. At the same time we want to use the bare minimum value which is still functional so the filesystem can be used in very low memory environments. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
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.
@behlendorf I've thought something like this would be a good idea for some time, but always wondered what a reasonable default would be. The allmem/32 seems quite reasonable.
Codecov Report
@@ Coverage Diff @@
## master #6659 +/- ##
==========================================
+ Coverage 67.61% 68.03% +0.41%
==========================================
Files 196 196
Lines 70349 70348 -1
Branches 13921 13921
==========================================
+ Hits 47569 47862 +293
+ Misses 17444 17111 -333
- Partials 5336 5375 +39
Continue to review full report at Codecov.
|
On 2017-09-20 12:16, kpande wrote:
what's with the code coverage spam?
It's a welcome change from Nigerian Prince and penis enlargement emails?
|
@kpande we're extending the automated testing to provide code coverage reports for PRs. |
Increase the default arc_c_min value to which whichever is larger, either 32M or 1/32 of total system memory. This is advantageous for systems with more than 1G of memory where performance issues may occur when the ARC is allowed to collapse below a minimum size. At the same time we want to use the bare minimum value which is still functional so the filesystem can be used in very low memory environments. Reviewed-by: Tim Chase <tim@chase2k.com> Reviewed-by: George Melikov <mail@gmelikov.ru> Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #6659
Increase the default arc_c_min value to which whichever is larger, either 32M or 1/32 of total system memory. This is advantageous for systems with more than 1G of memory where performance issues may occur when the ARC is allowed to collapse below a minimum size. At the same time we want to use the bare minimum value which is still functional so the filesystem can be used in very low memory environments. Reviewed-by: Tim Chase <tim@chase2k.com> Reviewed-by: George Melikov <mail@gmelikov.ru> Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#6659
Description
Increase the default arc_c_min value to which whichever is larger,
either 32M or 1/32 of total system memory. This is advantageous for
systems with more than 1G of memory where performance issues may
occur when the ARC is allowed to collapse below a minimum size.
At the same time we want to use the bare minimum value which is
still functional so the filesystem can be used in very low memory
environments.
Motivation and Context
By increasing the default
arc_c_min
on systems which have moretotal memory available it's possible to avoid some performance
pathologiies caused by the ARC collapsing due to competing
application demand for memory. The change complements recent
fixes such as 787acae which prevent the ARC from mistakenly
decreasing in size needlessly.
How Has This Been Tested?
zfs_arc_c_min
for their workload.Types of changes
Checklist:
Signed-off-by
.