My guess is that you have a loop that's not being terminated.
DBI tracing is a good idea - pointing a trace file to a /tmp file and
monitoring it to see what's going on, in conjunction with your source.
You may also want to inject some "print STDERR 'in func()'" throughout
your code and then monitor Apache's error log.
My last suggestion would be to write a test script that calls your
cgiapp directly and then run it with Devel::DProf. That will tell you
what a singular execution is like.
Feel free to hop on #cgiapp, too. :)
- Jason
John Saylor wrote:
hi
i have a CGI::App that is spiraling out of control. it's using up all
the memory and taking the server down with it. i can reproduce it, but
now i want to understand it.
does anyone have any suggestions of good practices or where to start?
Apache::Peek?
http://perl.apache.org/docs/1.0/guide/performance.html ?
DBI tracing?
it's apache 1.x running mod_perl on redhat fedora 4.
thx!
--
\js
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
