Right now we are shipping Satellite 6 with the KeepAlive option disabled in Apache. With this option enabled our UI is greatly sped up with some pages rendering in half the time, some examples: "CLOSE": close the connection "KA": KeepAlive is on ** Content Dashboard: CLOSE: 9.0S KA : 7.2S ** Facts: CLOSE: 1.0S KA : 0.2S ** Trends: CLOSE: 0.6S KA : 0.2S ** Audits: CLOSE: 0.6S KA : 0.3S ** Lifecycle Envs: CLOSE: 1.5S KA : 0.3S ** Activation Keys CLOSE: 3.5S KA : 1.6S ** All hosts: CLOSE: 1.9S KA : 1.1S ** Content Views: CLOSE: 4.0S KA : 1.6S We need to update the installer to flip this option to On in the httpd configuration file.
Created attachment 979757 [details] Satellite 6 CPU usage KeepAlive Off/On during Capsule Syncs
Created attachment 979758 [details] Satellite 6 External Capsule CPU usage KeepAlive Off/On during Capsule Syncs
In addition to the Web UI speed ups, KeepAlive reduces CPU usage on Satellite 6 and external Capsules. I have attached two graphs showing the cpu usage of Satellite 6 and a single external capsule while Satellite 6 was syncing a single repository of 2048 RPMs to 20 capsules concurrently.
hi please provide verfication steps thanks
TESTPLAN: Verify that the KeepAlive is On in: /etc/httpd/conf/httpd.conf PidFile run/httpd.pid Timeout 120 KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 15 if this is Off then this bug fails, if KeepAlive is On, it passes.
VERIFIED: # rpm -qa | grep foreman foreman-1.7.2.24-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch foreman-libvirt-1.7.2.24-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch hp-sl2x170zg6-02.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-sl2x170zg6-02.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-gce-1.7.2.24-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch foreman-ovirt-1.7.2.24-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch foreman-postgresql-1.7.2.24-1.el7sat.noarch foreman-debug-1.7.2.24-1.el7sat.noarch foreman-vmware-1.7.2.24-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch foreman-proxy-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch hp-sl2x170zg6-02.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch ruby193-rubygem-foreman_docker-1.2.0.14-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-compute-1.7.2.24-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.14-1.el7sat.noarch steps: Verify that the KeepAlive is On in: /etc/httpd/conf/httpd.conf ServerName "hp-sl2x170zg6-02.rhts.eng.bos.redhat.com" ServerRoot "/etc/httpd" PidFile run/httpd.pid Timeout 120 KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 15 KeepAlive is on
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days