Closed Bug 151209 (slow-bugzilla) Opened 22 years ago Closed 22 years ago

Bugzilla seems to be much slower since the upgrade

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: moz, Assigned: endico)

References

()

Details

Since the upgrade to the new version of Bugzilla, all bugzilla activities seem to be much slower. I even get connection refused messages. But probably it isn't related to the update at all.
Alias: slow bugzilla
Blocks: 150783
Bug resolutions in the "latest reported bug list" get updated only after a very long time, this makes bug triaging quite a pain.
I actually wonder whether the list gets updated at all. This bug isn't yet in the list and there's already a whole bunch of bugs newer than this one.
Adding bug 151281, some perf. work I did on duplicates.cgi. Gerv
Depends on: 151281
What else is the cause of this ? It's been pretty bad trying to search with this bug open :(
The list won't get updated if bugzilla is very busy, because its a spearate process which updates the shadowdb.
Depends on: bz-perf
Removing spaces from alias. Aliases should not contain spaces because they will confuse Bugzilla in bug lists (like the dependency lists).
Alias: slow bugzilla → slow-bugzilla
Are people still experiencing a lot of slowness?
No, it's seems to be back to normal.
I received one report of intermittent slowness which I think was caused by someone running multiple simultaneous queries trying to get all bugs in the database (a known DOS). Otherwise the severe post-upgrade performance problems seem to be resolved, so I'm resolving this bug. If you still have problems and can pinpoint them (a particular query, a certain time of day) please file a new bug about it.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
I believe the all-bug queries are caused by Mozilla bugs. I've seen it on my system before.
No longer depends on: bz-perf
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.