Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 229858 - Regularly slow bugzilla
Summary: Regularly slow bugzilla
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: devel
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-23 20:28 UTC by Karl Lattimer
Modified: 2013-06-24 02:44 UTC (History)
1 user (show)

Fixed In Version: 2.18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-11-01 18:55:37 UTC

Attachments (Terms of Use)

Description Karl Lattimer 2007-02-23 20:28:53 UTC
Redhat bugzilla is rediculously slow at times. Logins especially, any chance it
could be updated or moved onto better servers which are as responsive as gnome
bugzilla for instance?

Comment 1 ferg2k 2007-03-26 08:49:15 UTC
Bugzilla does not cope well with large datasets.  This is mostly due to some
vastly inefficient SQL generated by  Add table-level locking into the
mix and you've got an even bigger headache.

Your main solutions will be in two areas.

DB settings:
 - Shift as many tables as you can into innoDB.  Its row-level locking will help
a lot versus myisam.  Note you'll have to keep myisam for full-text search of
the comments table
 - Use a shadowdb host for searches.
 - Index everything
 - Boost your ram.
 - Watch for temp tables being written to disk.

Code changes
 - has some very inefficient JOINs.
 - show the output of a search with added '&debug=1' to your friendly local dba. 
 - keep your .js clean.  you've got some runaway errors that seem to hork
firefox pretty badly.
 - the groups code is horribly inefficient.  it can add hundreds of permissions
checks to the display of a single bug.

Take a look at where you load is going, and if cpu is an issue.  If you're
seeing high perl and apache load, you might want to reconsider public access to

Comment 2 David Lawrence 2007-11-01 18:55:37 UTC
Should be improved now. Closing.

Note You need to log in before you can comment on or make changes to this bug.