Bug 823309

Summary:	Performance problems when filing a new bug with many components
Product:	[Community] Bugzilla	Reporter:	Dan Mashal <dan.mashal>
Component:	Performance	Assignee:	Simon Green <sgreen>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.2	CC:	apevec, dwmw2, ebaak, h1k6zn2m, mizdebsk, rc040203, sgreen
Target Milestone:	4.2-1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.2.1-1.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-22 11:52:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	786624

Description Dan Mashal 2012-05-20 19:46:26 UTC

Description of problem:

Bugzilla has performance issues when creating a new bug.

Version-Release number of selected component (if applicable):

4.2

How reproducible:

Easy

Steps to Reproduce:
1. Login
2. Click New
3. Choose Fedora

  
Actual results:

Web browser spins for 2 minutes

After about 2 minutes you are presented with the create bug screen.

Expected results:

Should take you to new bug screen instantly.

Additional info:

None.

Comment 1 Mikolaj Izdebski 2012-05-21 14:06:07 UTC

I have the same problem.
The direct link to the page causing the problem is:
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora

Usually I need to wait for about 2-3 minutes for the page to load,
but sometimes it fails to load with the following error:

502 Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /enter_bug.cgi.

Reason: Error reading from remote server

Apache Server at bugzilla.redhat.com Port 443

Comment 2 Simon Green 2012-05-22 05:48:39 UTC

*** Bug 823760 has been marked as a duplicate of this bug. ***

Comment 4 Simon Green 2012-05-22 11:54:21 UTC

This will be fixed in an release that will be put live in the next few hours.

If a product has more than 200 components, we will use AJAX to get the component information, rather than load all the information on the page itself.

  -- simon

Comment 5 Simon Green 2012-05-22 15:10:35 UTC

*** Bug 824006 has been marked as a duplicate of this bug. ***

Comment 6 Simon Green 2012-05-22 15:10:53 UTC

*** Bug 823997 has been marked as a duplicate of this bug. ***

Comment 7 Simon Green 2012-05-22 21:25:40 UTC

This change is now live.

Comment 8 Simon Green 2012-05-22 22:01:34 UTC

*** Bug 823958 has been marked as a duplicate of this bug. ***

Comment 9 Simon Green 2012-05-23 00:26:42 UTC

*** Bug 823496 has been marked as a duplicate of this bug. ***

Comment 10 Dan Mashal 2012-05-23 04:20:47 UTC

Thanks Simon.