Red Hat Bugzilla – Bug 1313723
Dashboard loading extremely slow (30+ seconds)
Last modified: 2016-07-27 05:03:35 EDT
Dashboard loading a bit slow
Updated to increase the severity. The dashboard is very slow and often takes beyond 30 seconds to load which is unacceptable.
Needs to be sub 2-3 seconds.
Moving to POST since upstream bug http://projects.theforeman.org/issues/13993 has been closed
Applied in changeset commit:katello|45d3394b210f0fc0ddd44ff6562d26cf8d6595c9.
A new satellite 6.2-beta4 snap build took 6+ seconds to load and it is a brand new satellite without much data. I will continue to test with more data, but failing this bug since expectation is 2 to 3 seconds as per Comment 2.
I added libvirt provisioning and added a host. I also discovered/provisioned two hosts via discovery plugin. The dashboard still took 6+ seconds to load.
(discussed on IRC, but just to keep the bz in sync)
I suspect there is a different issue making the dashboard take 6+ seconds, vs the 30+ seconds bug.
I will investigate today.
I tested with firefox, here is how I did it:
* load dashboard page
* open developer tools (ctrl-shift-I), select network tab
* refresh page again (just regular, not shift-refresh)
If you want to remove bandwith as a factor, one way is to right click on the dashboard's load time in the network tab, and select "copy as curl". you can then paste that curl command onto a system that you know has a fast connection to the Satellite, and get the timing there. I typically add "-sk" to the curl command and pipe it to /dev/null since it can be a lot of output and I'm only interested in the timing :) Note that this does not fetch any images or JS, so it's not a true test, but is good for isolating issues.
If you still see 6+ seconds with the curl test, let me know and we can look further.
Tested in Satellite 6.2 Beta Snap 5.1. I see the loading times averaging between 2 to 3 seconds. I am marking this bug VERIFIED now.
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.