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
Created attachment 1588614 [details] developer_catalog_HAR
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?
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.
As comment 4, the performance is acceptable now. Verify this bug. io.openshift.build.commit.id=3d9532a92e0b2643418b8a51266cacdaec163a12
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