It *should* handle all connection requests.
The timing happens in the LogTrace() funtion in nslog/nslog.c. That trace
generally fires last to do logging to the access log, and the request
execution time is computed by comparing the time that LogTrace() was called
to the time returned by Ns_ConnStartTime().
Probably is a better way to do this, but this will at least give you a
consistent baseline to compare page execution times.
I don't have any analysis scripts, but would suggest looking at R.
- n
On 4/11/07, John Buckman <[EMAIL PROTECTED]> wrote:
I added server-side logging of ADP page execution a while back. Maybe that
would help you?
ns_section "ns/server/server1/module/nslog"
ns_param logreqtime true
Yes, that's great.
Will it also log ns_register_proc pages?
Have you written anything to crunch the numbers? If not, no problem, I can
do that.
-john
[MacBook-Pro:~] nfolkman% tail -f
/usr/local/aolserver/servers/server1/modules/nslog/access.log
192.168.1.129 - - [11/Apr/2007:10:46:28 -0400] "GET /flash/ HTTP/1.1" 200
191 "" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: 1.8.1.3)
Gecko/20070309 Firefox/2.0.0.3" 0.106342
192.168.1.129 - - [11/Apr/2007:10:46:28 -0400] "GET /favicon.ico HTTP/1.1"
404 534 "" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: 1.8.1.3)
Gecko/20070309 Firefox/2.0.0.3" 0.000361
On 4/11/07, John Buckman < [EMAIL PROTECTED]> wrote:
>
> 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.
>
--
Nathan Folkman
[EMAIL PROTECTED]
--
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.
--
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.
--
Nathan Folkman
[EMAIL PROTECTED]
--
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.
