-
Notifications
You must be signed in to change notification settings - Fork 103
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
limit cache dir size to about 60% of free space #3693
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Ornela Marić <[email protected]>
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 issue you are trying to fix here is present only on 4.3 where there is a bug in the configure-proxy not updating the cache size.
So please remove that tuning snippet, it is not relevant for 5.0 and later.
In general, {suse} recommends to adjust the value for the cache directory to about 60 % of available free space. | ||
Users can set the [option]``cache_dir`` option in the [path]``squid.conf`` manually. | ||
|
||
For more information, see xref:specialized-guides:large-deployments/tuning.adoc#tune_proxy[]. |
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.
This is not correct.
- 60% is very small here because there is nothing else taking the storage.
To be safe we can follow rule on squid configuration, that is using 80% of the space.
We recommend to be this 100G, same as the storage for that partition. Which will be the default in 5.1.
- users cannot modify
squid.conf
anymore. This value is set when generating proxy configuration on the server.
* SUSE/spacewalk#26396 * #3693 * Update modules/specialized-guides/pages/large-deployments/tuning.adoc * Apply suggestions from code review
For a link to rendered output, see https://github.com/SUSE/spacewalk/issues/26396.