We've extensively experimented with this option but without a proper Perl side cgi module this is not going to improve much, your best bet is to use a ramdrive for the whole perl environment and a simple cgi-wrapper to access Perl via fast_cgi, much the same as tcp->php-cgi works. Use a pool (upstream) to prevent blocking.
Basically the problem is shared environments and all the dangers that come with this. Typically Lua is much better suited for this but Lua ain't php or Perl, what's needed to solve this permanently is a Lua API which can expose php, python and Perl code in a non-blocking fashion. We're still experimenting with such API but getting stuck with blocking issues.
Basically the problem is shared environments and all the dangers that come with this. Typically Lua is much better suited for this but Lua ain't php or Perl, what's needed to solve this permanently is a Lua API which can expose php, python and Perl code in a non-blocking fashion. We're still experimenting with such API but getting stuck with blocking issues.