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.

Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/capsule_server_scalability

Section Number and Name: Table B.1. Puppet Scalability Using 4 CPUs with Red Hat Enterprise Linux 7 


Describe the issue: 

Customer has mentioned that the info in the below table for 20 resources per node looks very low.

So whether it's possible to complete the table with 50, 100, 200 and 300 resources?



Table B.1. Puppet Scalability Using 4 CPUs with Red Hat Enterprise Linux 7 (Recommended)
Puppet Managed Resources per Host	Run-Interval Distribution

1                                      3000-2500

10                                     2400-2000
	
20                                     1700-1400

50   ?

100  ?

200  ?

300  ?



Suggestions for improvement: 




Additional information: