in reply to Re: Benefiting from Devel::Profile or Devel::FastProf
in thread Benefiting from Devel::Profile or Devel::FastProf

Okay, Plack looks like it will help... (does PSGI need to replace CGI), however, I am confused about one thing still. Was the AUTOLOAD caused because my code called an undefined subroutine? Is it the values passed in, or the subroutine itself not loaded (would Autoloader solve it).

I am pretty sure I can restructure my code so it is unnecessary, but don't even know where to start. Could you point me in the right direction, or do I need to supply my code?

Thanks a lot

p.s. your perltoot link just sends to super search, not the perldoc (if that's what you were going for)

  • Comment on Re^2: Benefiting from Devel::Profile or Devel::FastProf

Replies are listed 'Best First'.
Re^3: Benefiting from Devel::Profile or Devel::FastProf
by Anonymous Monk on Jun 22, 2011 at 16:58 UTC
    AUTOLOAD is an interesting gamble. It allows a faster module load time while slowing the 1st invocation of a number of a module's subroutines/methods. If you use few of those subroutines, the gamble pays off. If you use many.....

    In your case, CGI::AUTOLOAD is the from the CGI module. To fix the situation you can either call fewer of the subroutines (probably not realistic) or do as the above response suggests and make those 1st invocations far fewer in percentage by allowing each instance of your perl program to handle more than one request.

    To see perltoot you can use perldoc perltoot on the command line, or ask for perltoot on perldoc.perl.org . perl comes with a wealth of documentation.

    TJD