Project

General

Profile

Actions

Bug #5841

closed

Foreman dashboard slow in 1.5 for non admin users

Added by Chuck Schweizer over 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Performance
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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

foreman_slow_non_admin_dashboard.txt foreman_slow_non_admin_dashboard.txt 348 KB debug output Chuck Schweizer, 05/20/2014 07:21 PM

Related issues 4 (0 open4 closed)

Related to Foreman - Bug #2982: Non Admin user Dashboard load is very slow with a large number of mangaged nodesResolved08/28/2013Actions
Related to Foreman - Bug #3122: when fact filters are added to a user, error column reference "id" is ambiguous for dashboard and fact_valuesClosed09/19/2013Actions
Related to Foreman - Bug #7009: N+1 hosts query in dashboard pageClosedOhad Levy08/10/2014Actions
Related to Foreman - Bug #8817: PGError: ERROR: missing FROM-clause entry for table "hostgroups"ClosedDominic Cleal12/31/2014Actions
Actions #1

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #2982: Non Admin user Dashboard load is very slow with a large number of mangaged nodes added
Actions #2

Updated by Dominic Cleal over 9 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
Actions #3

Updated by Dominic Cleal over 9 years ago

  • Difficulty deleted (easy)
Actions #4

Updated by Ohad Levy over 9 years ago

Dominic, did you investigate on this? Any reason why the ID's are added instead of INNER query?

Actions #5

Updated by Dominic Cleal over 9 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.

Actions #6

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #7009: N+1 hosts query in dashboard page added
Actions #7

Updated by Dominic Cleal about 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Dominic Cleal
Actions #8

Updated by The Foreman Bot about 9 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/1995 added
  • Pull request deleted ()
Actions #9

Updated by Dominic Cleal about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #10

Updated by Dominic Cleal about 9 years ago

  • translation missing: en.field_release set to 29
Actions #11

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #8817: PGError: ERROR: missing FROM-clause entry for table "hostgroups" added
Actions #12

Updated by Dominic Cleal almost 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.

Actions

Also available in: Atom PDF