Bug #5841
closed
Foreman dashboard slow in 1.5 for non admin users
Description
Previous ticket that fixed the issue for foreman 1.4
http://projects.theforeman.org/issues/3122
http://projects.theforeman.org/issues/2982
This foreman instance has 25,036 puppet clients reporting to it.
Files
Updated by Dominic Cleal over 10 years ago
- Related to Bug #2982: Non Admin user Dashboard load is very slow with a large number of mangaged nodes added
Updated by Dominic Cleal over 10 years ago
- Related to Bug #3122: when fact filters are added to a user, error column reference "id" is ambiguous for dashboard and fact_values added
Updated by Ohad Levy over 10 years ago
Dominic, did you investigate on this? Any reason why the ID's are added instead of INNER query?
Updated by Dominic Cleal over 10 years ago
Ohad Levy wrote:
Dominic, did you investigate on this? Any reason why the ID's are added instead of INNER query?
Not in depth, but I saw here that it was done deliberately: https://github.com/theforeman/foreman/blob/develop/app/models/report.rb#L36-L37
It might be we can use the authorized scope directly, but I haven't tested.
Updated by Dominic Cleal over 10 years ago
- Related to Bug #7009: N+1 hosts query in dashboard page added
Updated by Dominic Cleal almost 10 years ago
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
Updated by The Foreman Bot almost 10 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/1995 added
- Pull request deleted (
)
Updated by Dominic Cleal almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset d50c79908831be65da0b0005e438c9e819db613a.
Updated by Dominic Cleal almost 10 years ago
- Translation missing: en.field_release set to 29
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #8817: PGError: ERROR: missing FROM-clause entry for table "hostgroups" added
Updated by Dominic Cleal over 9 years ago
This was shipped in 1.7.1 but will be reverted in 1.7.3 as it caused a more severe issue recorded in #8817. The change remains in the 1.8/1.9 branches, where I hope to have a better solution to fix both.