Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionPradeep Kumar Surisetty
2017-01-29 10:51:11 UTC
Description of problem:
Have 6k hosts registered to setup.
Selected an errata which is applicable for 4K+ hosts. Took more than 6 mins to list
content -> errata -> any errata -> Applicable content Hosts of respective errata
GET https://gprfc018.sbu.lab.eng.bos.redhat.com/api/v...h=(+applicable_errata+%3D+%22RHBA-2015:2115%22+) 200 OK 6m 35s
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.with Scale environment
content -> errata -> any errata -> Applicable content Hosts of respective errata
2.
3.
Actual results:
List Applicable content Hosts of respective errata at scale takes long time
Expected results:
Take lesser time to open
Additional info:
Comment 3Pradeep Kumar Surisetty
2017-01-29 11:18:31 UTC
Comment 7Pradeep Kumar Surisetty
2017-01-29 11:26:01 UTC
Created attachment 1245538[details]
memory usage per process
while true; do (date && ps aux --sort -rss | head -n20) >> /var/log/foreman/ps-aux2.log; sleep 60; done
I have configured logging of queries longer than 1sec:
log_min_duration_statement = 1000
and refreshed the page, but it did not shown anything. Then I have displayed number of transactions processed by server (well, one transaction can have 0 - more queries), refreshed the page and checked the transaction count again:
postgres=# SELECT sum(xact_commit+xact_rollback) FROM pg_stat_database;
sum
--------
810380
(1 row)
...refresh and wait:
postgres=# SELECT sum(xact_commit+xact_rollback) FROM pg_stat_database;
sum
--------
939428
(1 row)
I.e. almost 130k transactions to refresh one page. Well, there is something else running on the Satllite, but still.
I'm not seeing this behavior on the reproducer anymore. I'm selecting a specific Errata and going to the Content Hosts tab. Is this the correct workflow?
Comment 12Pradeep Kumar Surisetty
2017-02-23 18:02:55 UTC
*** This bug has been marked as a duplicate of bug 1417642 ***