Hi all,

S=
o for many years I've been slack and writing perl scripts to do various thi=
ngs - but never needed more than the normal apache +ExecCGI and Template To=
olkit.

One of my sites has become a bit more popul=
ar, so I'd like to spend a bit of time on performance. Currently, I'm seein=
g ~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 i=
ts 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 - b=
ut 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 wou=
ld 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 globa=
l vars and a lot of common subs - and for whatever reason (can't find anyth=
ing on Google as to why), none of the subs are recognised in the main scrip=
t when loaded via ModPerl::PerlRun.

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