Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1312680

Summary:	increase shared_buffers in postgresql.conf to 256MB
Product:	Red Hat Satellite	Reporter:	Pradeep Kumar Surisetty <psuriset>
Component:	Performance	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.7	CC:	bkearney, cduryee, ekohlvan, mmccune, psuriset, rjerrido
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-22 09:42:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1312098

Description Pradeep Kumar Surisetty 2016-02-28 18:48:04 UTC

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:

Comment 1 Chris Duryee 2016-03-08 01:17:09 UTC

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.

Comment 2 Pradeep Kumar Surisetty 2016-04-18 11:40:30 UTC

This need to run on scale to reproduce. Setting up infrastructure to register 5000-10000 systems to satellite/capsule. Keep you updates.

Comment 3 Chris Duryee 2016-06-01 15:08:33 UTC

Per email thread, lets do 256M as default for shared_buffers.

Comment 4 Pradeep Kumar Surisetty 2016-06-01 15:26:44 UTC

Based on scale limit, we could increase it to 512M if needed

Comment 6 Rich Jerrido 2016-06-01 17:57:14 UTC

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.

Comment 7 Pradeep Kumar Surisetty 2016-10-31 06:26:34 UTC

Can we change this in 6.3/6.2?

Comment 8 Pradeep Kumar Surisetty 2017-07-07 03:27:19 UTC

shared_buffer needs to be increased for scale runs
can we make this change as default config

Comment 13 Ewoud Kohl van Wijngaarden 2018-06-22 09:42:32 UTC

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 ***