Bug 1297683
Summary: | "Error: Request Timeout" from hammer when asked to show >400 content hosts | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Christian Horn <chorn> | |
Component: | WebUI | Assignee: | Andrew Kofink <akofink> | |
Status: | CLOSED DUPLICATE | QA Contact: | Katello QA List <katello-qa-list> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 6.1.4 | CC: | akofink, bbuckingham, bkearney, dlobatog, ehelms, erinn.looneytriggs, inecas, jsherril, mmccune, smeyer, sshtein, sthirugn | |
Target Milestone: | Unspecified | Keywords: | Performance, Triaged | |
Target Release: | Unused | |||
Hardware: | All | |||
OS: | Linux | |||
URL: | http://projects.theforeman.org/issues/16010 | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1426378 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-05 09:25:09 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1296845, 1426378 |
Description
Christian Horn
2016-01-12 08:49:47 UTC
I suspect issues in the code, a quick fix would be if hammer would atleast use paging by itself. I.e. paging to 400 results by default. Moving 6.2 bugs out to sat-backlog. Created redmine issue http://projects.theforeman.org/issues/16010 from this bug Upstream bug component is WebUI How is this WebUI when it deals with Hammer/API? It seems like rendering the view takes the majority of the time: Completed 200 OK in 68556ms (Views: 52481.4ms | ActiveRecord: 14506.9ms) Performance improvement can be gained by including the proper tables (N+1 queries) at the beginning, rather than requesting more data from the DB in the view layer: Before: 2016-08-09T09:28:22 ef4eff65 [app] [I] Completed 200 OK in 30798ms (Views: 28758.6ms | ActiveRecord: 1144.1ms) 2016-08-09T09:30:29 ef4eff65 [app] [I] Completed 200 OK in 29078ms (Views: 27504.6ms | ActiveRecord: 1114.1ms) 2016-08-09T09:31:04 ef4eff65 [app] [I] Completed 200 OK in 29546ms (Views: 27802.8ms | ActiveRecord: 1237.9ms) Average: 29807.3ms After: 2016-08-09T09:24:13 ef4eff65 [app] [I] Completed 200 OK in 24099ms (Views: 22732.9ms | ActiveRecord: 705.7ms) 2016-08-09T09:25:48 ef4eff65 [app] [I] Completed 200 OK in 22791ms (Views: 21248.9ms | ActiveRecord: 621.4ms) 2016-08-09T09:26:14 ef4eff65 [app] [I] Completed 200 OK in 21944ms (Views: 20642.8ms | ActiveRecord: 683.7ms) Average: 22944.6 That's 23% faster. Andrew, upstream bug is set to WebUI, so that was copied to this bug. Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16010 has been resolved. Bryan, it looks like the release for the Foreman issue (http://projects.theforeman.org/issues/16646) is set to 1.14. Setting as triaged as there's a fix already upstream Please add verifications steps for this bug to help QE verify Verification could be to look for N+1 warnings in the production.log while requesting the hosts page before applying. The warnings should not show up after applying the fix, and you should be able to notice a speed improvement in the response for a Satellite with hundreds of hosts. Cherrypicks provided in https://bugzilla.redhat.com/show_bug.cgi?id=1419667 *** This bug has been marked as a duplicate of bug 1419667 *** |