This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2279313 - The content views pagep[WebUI] is taking so long
Summary: The content views pagep[WebUI] is taking so long
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.14.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: 6.15.1
Assignee: Samir Jha
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-06 13:53 UTC by Odilon Sousa
Modified: 2024-06-07 01:11 UTC (History)
11 users (show)

Fixed In Version: rubygem-katello-4.11.0.11-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2266197
Environment:
Last Closed: 2024-06-06 17:37:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36976 0 Normal Closed Very slow content view list loading 2024-05-06 13:53:44 UTC
Github Katello katello pull 10911 0 None Merged Fixes #36976 - Too many audit records slow down CV loading 2024-05-06 13:53:44 UTC
Red Hat Issue Tracker   SAT-24959 0 None Migrated None 2024-06-06 17:37:10 UTC
Red Hat Knowledge Base (Solution) 7058645 0 None None None 2024-05-06 13:53:44 UTC

Comment 1 Vladimír Sedmík 2024-05-23 12:43:13 UTC 
Verified in 6.15.1 snap 1.0. 

Steps to verify:
1. Import maifest and sync 30 RH repos.
2. Creat a CV and add all repos from 1.
3. Clone the CV 39x so that we end up with 40 CVs.
4. Creat 3 LCEs above the Library.
5. Publish all the CVs and promote them to all LCEs.
   At this point you have ~38200 audits.
6. List the CVs via hammer and measure the time:
   [root@sat ~]# time hammer content-view list

At the reproducer VM (6.14.3 snap 2.0) the listing took 7.754 seconds in average.
At the fixed VM (6.15.1 snap 1.0) the listing took 2.725 seconds in average.
This means 2.85 times faster listing with the given setup and the ratio would be even higher for bigger setup with more repos/CVs/audits.
Comment 3 Eric Helms 2024-06-06 17:37:11 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.