Change Multiple Bugs process is extremely slow

RESOLVED DUPLICATE of bug 215320

Status

()

RESOLVED DUPLICATE of bug 215320
13 years ago
13 years ago

People

(Reporter: s.blair, Unassigned)

Tracking

2.18.1
x86
Windows XP

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322; InfoPath.1)
Build Identifier: Bugzilla v2.18.1

When changing multiple bugs, Bugzilla becomes completely non-responsive to other users and is incredibly slow in processing the change for multiple bugs.

It is actually faster changing bugs individually than doing a multiple change as affecting a change on multiple bugs is 

Reproducible: Always

Steps to Reproduce:
1. Select a large number of bugs ~25 or more.
2. Effect a change on them all, such as changing Target or changing Status.
3. Feel the pain while it churns on them and blocks all other access to Bugzilla by other users.



Expected Results:  
The process should execute much faster at least as fast as changing n times the time it takes for a single bug.

Also it should not completely block access to bugzilla queries by other users.

Comment 1

13 years ago
do you have many products and/or groups in your installation?
Please update to the latest release on the 2.18 branch.  This is a known issue which is already fixed in the latest 2.18.x version (2.18.5 is current on the the 2.18 branch).

It's an issue with warnings filling up apache's stderr buffer.
Whiteboard: DUPEME
Version: unspecified → 2.18.1
Found it (thanks LpSolit).  This was fixed in 2.18.2.  Being on 2.18.1 you're also missing a bunch of security fixes as well.  You should really upgrade.

*** This bug has been marked as a duplicate of 215320 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.