Bug #15366
closedErrata Install to Content Host takes too long and doesn't scale well
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1288152
Description of problem:
When applying (installing) errata on a Content Host from the server, it takes a very long time.
For example, installing ~556 errata on a single content host was observed to take ~44 minutes. Most of that time (~36 minutes) was during the 'initiating the install' phase of the task (i.e. executing the pulp consumer content install). While this may not sound too bad a first glance, it won't scale well as the behavior is linear. As a result, if there were 100 content hosts, that same action could take ~3 days.
Version-Release number of selected component (if applicable):
pulp-server-2.6.0.17-1.el7sat.noarch
pulp-rpm-plugins-2.6.0.17-1.el7sat.noarch
ruby193-rubygem-katello-2.2.0.76-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. install Satellite 6.1.4
2. import a manifest
3. enable and sync the RHEL 6Server RPM repo
4. create a content view containing the RHEL 6Server RPM repo and publish it
5. register a RHEL 6.5 client to the above content view
6. initiate an errata install from the UI
(Hosts -> Content Hosts -> select the host -> Errata -> scroll through
all of the errata, select them and 'Apply Selected')
Actual results:
Observe that the errata are installed on the content host; however, it takes a very long time to initiate and execute the task.
Expected results:
We need to investigate why it is taking so long to initiate the errata install and look for ways to optimize it to improve performance.
Additional info:
Attaching a foreman debug from the server where the above scenario was executed.