You could probably get a huge performance gain without changing any code—if it’s presently well behaved and scoped—just by going persistent with running it. This is mostly how everyone does it and why understanding prior art is so important and will save you much more time than it costs to learn. Template::Toolkit and Catalyst are both fairly slow for example. Catalyst is all but useless run as CGI and TT2 compiles and caches itself to improve performance and only resorts to recompiling from the original templates when they have changed. Even the check interval for changes is tunable.
Run any one of your CGIs like so and visit it at port 8080 on whatever host–
starman --listen :8080 -MPlack::App::WrapCGI \ -e 'Plack::App::WrapCGI->new( script => "your.cgi" )'
In reply to Re^3: snakes and ladders
by Your Mother
in thread snakes and ladders
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |