Bugzilla handling heavy load

[David Miller]

Sam Fu wrote on 8/15/07 4:45 PM:
> Hey All, I was wondering if anyone had any information about this.  I’ve
> managed to Web 2.0/Ajax Bugzilla 3.0 for my company’s use.  From a UI
> and user experience perspective it has been well received.  The only
> adverse effect that I’ve noticed from doing this is the heavy load in
> terms of CPU usage on the server.  This is due in part to asynchronous
> connections that each individual calls to the server.  While looking at
> the server I’ve noticed that Perl handles each individual request by
> creating a new process.  So if an individual makes 5 requests to the
> server (to update 5 different parts of the UI), the server handles it by
> opening 5 individual Perl.exe processes rather than, for example keeping
> a process open and running thread support. 

This is probably better to go on the support list than here (see
http://www.bugzilla.org/support/ ) so I'm CCing there on my reply (and
please follow-up there if you reply).

This sounds like exactly the problem mod_perl was designed to tackle.
It embeds the perl interpreter into the webserver and keeps Bugzilla in
memory so that requests can be served rapidly without the overhead of
spawning a new Perl process on every request.  Bugzilla 3.0 supports
mod_perl, so as long as you followed good coding practices while making
your modifications, you should be okay.  (See
http://www.bugzilla.org/docs/developer.html#perl and
https://bugzilla.mozilla.org/show_bug.cgi?id=173629 )

Instructions for setting up Bugzilla with mod_perl are at
http://www.bugzilla.org/docs/3.0/html/configuration.html#http-apache-mod_perl

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/