Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #2937] Log View unusable with large logentries table #859

Closed
icinga-migration opened this issue Aug 3, 2012 · 2 comments
Closed
Labels
bug
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Aug 3, 2012

This issue has been migrated from Redmine: https://dev.icinga.com/issues/2937

Created by tgelf on 2012-08-03 12:17:19 +00:00

Assignee: (none)
Status: Resolved (closed on 2012-08-03 14:07:14 +00:00)
Target Version: 1.8
Last Update: 2012-08-03 14:19:01 +00:00 (in Redmine)


Log View is so terrible slow that it cannot be used, at least once you have a few million log entries in you database. This is at least true for MySQL. Fixing it is pretty easy, the INNER JOIN makes MySQL believe that it has to copy around a lot of stuff for it's WHERE/ORDER Voodoo. There is an easy workaround for this: just replace the INNER with an OUTER JOIN.

This is done in app/modules/Api/config/views/misc.xml, section TARGET_LOG. Replace 'INNER JOIN l.instance' with 'LEFT JOIN l.instance', and that's it. Query time went down from minutes (!) to a fraction of second here.

Changesets

2012-08-03 12:22:48 +00:00 by mhein 4c3a848

Performance fix for log view, fixes #2937

2012-08-03 12:23:22 +00:00 by mhein 80c9229

Performance fix for log view, fixes #2937
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Aug 3, 2012

Updated by mhein on 2012-08-03 14:07:14 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset 80c9229.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Aug 3, 2012

Updated by mfriedrich on 2012-08-03 14:19:01 +00:00

  • Target Version set to 1.8
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.