in reply to Running nytprof in classic asp

What are you hoping to learn from this?

Because usually , most everything your program does, you can profile outside of IIS or apache .... because for the most part the overhead of IIS or apache ... is fixed portion you cannot improve upon

See https://metacpan.org/pod/Devel::NYTProf::Apache for some caveats which probably apply to IIS as well

Replies are listed 'Best First'.
Re^2: Running nytprof in classic asp
by Anonymous Monk on Mar 27, 2014 at 09:01 UTC
    This supposed to be a proof of concept for monitoring an existing asp-perl application that has become too slow. I would like to see which part of the application is taking too much time and start the investigation from there. Is there a way I can profile those script out of IIS? Thanks.
[reply]

      Is there a way I can profile those script out of IIS?

      Theoretically , yes

      Practically, maybe -- NYTProf says it doesn't support it; maybe you can try one of the other/simpler profilers ....

      The PerlScript faq mentions nothing

      There are really only two things that can slow down scripts, and profiling isn't required to find them

      1) using too much memory and forcing memory swapping (look for and eliminate leaks in your program, buy more hardware/ram for your machine ... shorten restart interval ...

      2) network or database slowdown (nothing you can do about it from perl)

      I would recommend performing a code review looking at how your application manages memory and communication with network/database...

[reply]

In Section Seekers of Perl Wisdom