Bug 1728099

Summary: [Performance] It takes very long time to redirect Developer Catalog page to response user
Product: OpenShift Container Platform Reporter: shahan <hasha>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:33:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
developer_catalog_preview
none
developer_catalog_HAR none

Description shahan 2019-07-09 03:22:46 UTC
Created attachment 1588613 [details]
developer_catalog_preview

Description of problem:
 To redirect Developer Catalog  page take very long time to response user. From Performance tab of dev console, it shows the console was staying at idle status in most of loading time. The pages take 30 seconds more to show contents usually.

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-03-171807
a15ac81be7f7479b1d527a28c780fd09ce123710

How reproducible:
always

Steps to Reproduce:
1.click Catalog->developer catalog page  Page
2.
3.

Actual results:
The page take 40 seconds more even 60s to show contents usually.

Expected results:
Should show page in an acceptable time.

Additional info:
more info refer to attachments

Comment 1 shahan 2019-07-09 03:23:44 UTC
Created attachment 1588614 [details]
developer_catalog_HAR

Comment 3 shahan 2019-08-13 06:12:57 UTC
The response time control within 10 seconds. Particularly, the request api/kubernetes/apis/image.openshift.io/v1/namespaces/openshift/imagestreams?limit=250 will takes 9s+. 
Samuel, double confirm, is that acceptable response time range?

Comment 4 Samuel Padgett 2019-08-13 16:23:41 UTC
Given the extremely high latency and the fact that this is down from 40s, I'd say it's acceptable. This is really a worse case scenario. For context, the request for image streams took 283ms from my location to my cluster in us-east-2 and the page loaded quickly.

We can't use the same trick for image streams since we need more than the metadata to filter the builder images. We might be able to save a bit by using gzip on API responses, but I think for now the performance is acceptable.

Comment 6 shahan 2019-08-14 06:14:49 UTC
As comment 4, the performance is acceptable now.
Verify this bug.
io.openshift.build.commit.id=3d9532a92e0b2643418b8a51266cacdaec163a12

Comment 7 errata-xmlrpc 2019-10-16 06:33:23 UTC
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.

https://access.redhat.com/errata/RHBA-2019:2922