Moving ExecCGI to mod_perl - performance and custom 'modules'

Hi all,

So for many years I've been slack and writing perl scripts to do 
various things - but never needed more than the normal apache +ExecCGI 
and Template Toolkit.

One of my sites has become a bit more popular, so I'd like to spend a 
bit of time on performance. Currently, I'm seeing ~300-400ms of what I 
believe to be execution time of the script loading, running, and then 
blatting its output to STDOUT and the browser can go do its thing.

I believe most of the delay would be to do with loading perl, its 
modules etc etc

I know that the current trend would be to re-write the entire site in a 
more modern, daemon based solution - and I started down the Mojolicious 
path - but the amount of re-writing to save 1/3rd of a second seems to 
be excessive.

Would I be correct in thinking that mod_perl would help in this case?

I did try a basic test, but I have a 'use functions' in all my scripts 
that loads a .pm with some global vars and a lot of common subs - and 
for whatever reason (can't find anything on Google as to why), none of 
the subs are recognised in the main script when loaded via 
ModPerl::PerlRun.

So throwing it out to the list - am I on the right track? wasting my 
time? or just a simple mistake?

--
Steven Haigh

📧 [email protected] <mailto:[email protected]>
💻 https://www.crc.id.au <https://www.crc.id.au/>