I must request you for help. Within our company, we've installed Bugzilla 4. on Home windows machine. For running perl, we're presently using ActivePerl.

The issue is, that people have around 50 customers periodically querying the Bugzilla web service and server can't take this load. We've discovered, that it's triggered by perl.exe, that is being went throughout every request. Server workload (Processor chips) take presctiption 90% throughout peaks.

Maybe you have experienced this problems? Is any possible configuration, we are able to make, to enhance the performance?

We're using: Apache 2.2.17 and ActivePerl 5.8.9 b829. Thanks greatly ahead of time, it causes us (especially me) lots of trouble.

This can be a not unheard of problem as sites grow. And it is not particularly restricted to Perl either. You will find solutions. As you person pointed out, there's mod_perl, that is basically installed being an Apache module. You can use it inside a kind of simple version via Apache::Registry, or go completely by writing components that communicate with the Apache API each and every request phase. Whatever approach you are taking with mod_perl, you will find a couple of common notes: It's a persistent process, meaning (basically), Perl stays resident in one request to another, to another, to ensure that you eliminate startup costs. CGI scripts frequently can't be ported straight to mod_perl without some quantity of cleanup and refactoring. Because the script runs inside a persistent atmosphere, global variables don't totally reset themselves between demands, for instance. There is a whole listing of 'gotchas' to beat. To that particular finish, Apache::Registry is sort of simpler to cope with inside a mod_perl atmosphere, at the fee for not supplying 100% from the performance horsepower that programming for that API directly can offer. Nonetheless, it's an excellent compromise.

Another option is FastCGI, which you'll find out about at the FastCGI website.

Well crafted CGI scripts can be ported to mod_perl in order to FastCGI with a few effort. They are most likely minimal painful approaches, for your reason. Some scripts could be converted with hardly any cleanup. Others may need lots of work, but ought to be still possible.

Fortunately there's an array of helpful modules on CPAN to help you in making use of mod_perl, or FastCGI. Underneath the Apache::* hierarchy on CPAN, for example, you will find many tools that can use mod_perl. Regarding FastCGI, you'll even find Catalyst and Mojolicious-related modules to assist meld the 2, though individuals latter suggestions would most likely require some real refactoring.

I discovered Practical mod_perl to become useful like a beginning point (an O'Reilly book).

Food for thought: mod_perl