Bug 2279313

Summary:	The content views pagep[WebUI] is taking so long
Product:	Red Hat Satellite	Reporter:	Odilon Sousa <osousa>
Component:	Content Views	Assignee:	Samir Jha <sajha>
Status:	CLOSED MIGRATED	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.14.3	CC:	ahumbe, gformisa, jbhatia, jlenz, momran, osousa, pmoravec, rlavi, sajha, unixbasis, vsedmik
Target Milestone:	6.15.1	Keywords:	MigratedToJIRA, Performance, Regression, Triaged, WorkAround
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-katello-4.11.0.11-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2266197	Environment:
Last Closed:	2024-06-06 17:37:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.