Description of problem:
hammer erratum list command taking too much time to display erratum, if there are 10+ repositories synchronized into Satellite
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Synchronize 10 + Server RPMs and other repositories of different RHEL releases
2. Execute hammer erratum list which seems to be hung for a very long time and response/result is taking more than an hour to display i.e. time varies based upon the number of repositories it has to query.
With 10+ repositories time took to display the result was around
Should display the result immediately as REST API of the same does.
If we query the same information through REST API, the results are pretty fast.
could you please attach full output of hammer -d erratum list from the machine where you experienced the slowness? Thank you!
I have taken over this case from Nagoor.
I am attaching the full output of "# hammer -d erratum list --content-view "AMAT Certified RHEL 6 FY2017Q1 64-bit"" which was provided by the customer.
If you need anything else, let me know.
Thank you very much from the logs, Mihir.
From the timestamps in the log it seems the complete data was fetched in 3 minutes and the rest of the time was hammer trying to print it:
- started: 2016-11-30 22:50:24
- last response: 2016-11-30 22:53:29
- time - real: 02:18:58
- getting data took: 00:03:05
- print time: 02:15:53
It seems that printing tables is terribly suboptimal.
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17740 has been resolved.
Verified in Satellite 6.2.8 Snap 3
While there are no standards for errata count, the results below look like a significant improvement over the previous performance.
Satellite with 6,335 errata:
Satellite with 33,289 errata:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.