Description of problem: The shared_buffers configuration parameter determines how much memory is dedicated to PostgreSQL to use for caching data. By default satelitte 6.1 use lower value (32MB). Its set to lower because of other platforms. Recommended value is between 15% to25% of memory. Ex Content-host registration at scale needs th5s. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Is there an easy way to reproduce the issue that shared_buffers fixes? I don't know if giving shared_buffers 2.5-4GB would impact other components.
This need to run on scale to reproduce. Setting up infrastructure to register 5000-10000 systems to satellite/capsule. Keep you updates.
Per email thread, lets do 256M as default for shared_buffers.
Based on scale limit, we could increase it to 512M if needed
For Satellite 6.1, we increased the minimum system requirements to 12GB to accommodate (the removed in 6.2) elasticsearch. I suspect we'll have the required headroom to make this change without updating the system requirements. Would still add a release note or doc somewhere regarding the change.
Can we change this in 6.3/6.2?
shared_buffer needs to be increased for scale runs can we make this change as default config
We already have an RFE for this which exposes this as a parameter in foreman-hiera.yaml and increases the default to 512MB. *** This bug has been marked as a duplicate of bug 1440879 ***