Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/tuning_red_hat_satellite/tuning#tuning_passenger_for_puppet_4_related_workloads Section Number and Name: 5.2.4. Tuning Passenger for Puppet 4-related workloads Describe the issue: Puppet 4 does not run under Passenger, but as a standalone (Java) process and as such should be configured/tuned in /etc/sysconfig/puppetserver and /etc/puppetlabs/puppetserver/ and not /etc/httpd/conf.d/passenger.conf Also, given it's Java, not Ruby, different tuning settings will apply. Suggestions for improvement: Additional information:
(In reply to Evgeni Golov from comment #0) > Document URL: > https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/ > tuning_red_hat_satellite/ > tuning#tuning_passenger_for_puppet_4_related_workloads > > Section Number and Name: > 5.2.4. Tuning Passenger for Puppet 4-related workloads > > Describe the issue: > Puppet 4 does not run under Passenger, but as a standalone (Java) process > and as such should be configured/tuned in /etc/sysconfig/puppetserver and > /etc/puppetlabs/puppetserver/ and not /etc/httpd/conf.d/passenger.conf > > Also, given it's Java, not Ruby, different tuning settings will apply. > > Suggestions for improvement: > > Additional information: Hi Evgeni, This tuning actually relates to Passenger when the workload is mostly Puppet 4 based and does not really cover any tunings that should be applied to Puppet itself. Probably, we can title this section more inline with that purpose to reflect on that.