This will also display a list of all missing bugzilla modules that needs to be installed.
Execute the bugzilla īugzilla program will verify whether all the required perl modules are installed.
# tar xvfz /usr/save/bugzilla-3.4.6.tar.gz 5.
Extract the bugzilla*.tar.gz file to the apache document root directory as shown below.
Download latest Bugzilla tar ballĭownload the latest stable release from bugzilla download page.
Sorry if there's no silver bullet.If you don’t have apache, install is using yum based on LAMP install article, or install apache from source. This was a no-go prior to galileo, but fixing this is on our plate for Q3. Sourcing new batteries that don't cost an arm is in the works, but replacing batteries requires the machines be powered down. Right now, all our RAID controller batteries are dead, which means disk write cache is disabled. Disk performance on our database servers is suffering since our ageing servers require maintenance. This was not a problem before we had a local build server and local project vservers, but now with LAN access to CVS and downloads, some projects are building constantly, which uses resources. Our database slave server, which handles Bugzilla searches most of the time, is quite busy since it's our primary file server. I'm working with the Mylyn team so that we can optimize some things via some open bugs. Of course, while these queries run, the database gets slower, and incoming changes are blocked by locked tables from the point above. It's not uncommon to see six to nine MySQL threads working on Mylyn-related searches that usually end up being killed for taking too long. I see a fair amount of Mylyn queries that come in at the same time.
The table types are changed in Bugzilla 3.2, so I'm making this bug depend on the upgrade ( bug 244441). Because the BZ tables are MyISAM, table locking can introduce tremendous lag when some folks run large searches. More specifically (in no particular order): I know why it's slow before you even realize it's slow :-) The main reason is database-related. > people are running too many queries too often?Īh, I was expecting you. > Do you know the causes of the slowness? Just a wild guess, but perhaps some That might not sound like very much, but if your main task is to look at incoming bugzilla emails, you need to look at a good number of bugzilla entries for context, and having to wait 5-10 seconds for each bug kills productivity (and makes this part of my work even less enjoyable).ĭo you know the causes of the slowness? Just a wild guess, but perhaps some people are running too many queries too often? It just happens too often that I end up waiting for 5-10 seconds. I need to wait for the resulting page to make sure there is no conflict, and to check for misspelled email addresses when adding to the cc list. Ideally, that response time should be below a second.Īnother operation that should be fast is adding a comment, changing a target milestone, or adding someone to the cc list. One operation that needs to be fast is when I click on a link to a Bugzilla that I get the single bug page back in a reasonable response time. I am not talking about operations that by their very nature (e.g. Sorry for not being more specific, but Bugzilla is too slow for effectively working with it, too often.