www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael S.Fischer <mich...@auctionwatch.com>
Subject general/6773: Need finer elapsed service time granularity
Date Wed, 01 Nov 2000 03:11:22 GMT

>Number:         6773
>Category:       general
>Synopsis:       Need finer elapsed service time granularity
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Tue Oct 31 19:20:00 PST 2000
>Originator:     michael@auctionwatch.com
Currently in mod_log_config it looks like the elapsed service time (%T) is computed by taking
time(NULL) and subtracting r->service_time() from it.  Unfortunately, this doesn't provide
nearly the granularity we need to do useful performance analysis of our server-side code.

We would really love to see in a future Apache release a logging facility that can return
the elapsed request service time on the order of microseconds.  
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message