Bug #32269
Puppetserver 6+ really benefits from increased ReservedCodeCacheSize
Status:
Closed
Priority:
High
Assignee:
Category:
foreman-installer script
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Description
https://puppet.com/docs/puppet/6.21/server/tuning_guide.html suggests to increase ReservedCodeCacheSize. Technically this is needed when JRuby 9k is enabled. That was an option in 5 and default in 6. A value of 512m appears to be good default.
Associated revisions
History
#1
Updated by The Foreman Bot almost 2 years ago
Updated by - Assignee set to Ewoud Kohl van Wijngaarden
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-installer/pull/671 added
#2
Updated by The Foreman Bot almost 2 years ago
- Fixed in Releases 2.5.0 added
#3
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset installer|2bede0faa924a3c86fd06933fbcc7b9133d9d193.
#4
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
- Triaged changed from No to Yes
- Target version set to 2.5.0
- Category set to foreman-installer script
Fixes #32269 - Set ReservedCodeCache for Puppetserver
Puppetserver 6 really benefits from an increased ReservedCodeCache.
Puppet recommends this in their tuning guide1 and various deployments
have shown to greatly benefit from it. 512m appears to be a good default
since it works well even on small installs without real downsides.
[1]: https://puppet.com/docs/puppet/6.21/server/tuning_guide.html