You can also use Devel::DProf to find out in which subroutine the code needs so much time... e.g. write to the header something like
#! /usr/bin/perl -d:DProf
then run the script (needs write access to the current directory), and evaluate the trace with dprofpp -T or the like
Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"
In reply to Re: Debug a long-running CGI script?
by strat
in thread Debug a long-running CGI script?
by Murcia
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |