I'm wondering if anyone on this list has written code to "profile" a web site running under Aolserver.

By this, I mean, timing the start/stop time of every page, logging it, and then running a bit of analysis to find out what pages are the slowest running and which pages are the most commonly loaded, then multiplying the two (ie execution time x requests per day=total machine load per page per day)

In traditional systems programming, profiling is a common tool used to determine what code should be optimized. I'd like to do the same inside aolserver.

One efficient alternative I was thinking about would be to patch ns_log to include both the start request time, and the time the page was returned, in the log. That could be done if ns_log is called after the page is rendered, and I don't know if that's the case.

-john


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to