Received: (qmail 19409 invoked by uid 2012); 18 Mar 1998 16:38:28 -0000 Message-Id: <19980318163828.19408.qmail@hyperreal.org> Date: 18 Mar 1998 16:38:28 -0000 From: Jason Venner Reply-To: jason@idiom.com To: apbugs@hyperreal.org Subject: The %T directive in log_mod_config only gives 1 second resolution for timing requests X-Send-Pr-Version: 3.2 >Number: 1966 >Category: mod_log-any >Synopsis: The %T directive in log_mod_config only gives 1 second resolution for timing requests >Confidential: no >Severity: non-critical >Priority: medium >Responsible: contrib@apache.org >State: closed >Class: change-request >Submitter-Id: apache >Arrival-Date: Wed Mar 18 08:40:00 PST 1998 >Last-Modified: Wed Mar 18 10:20:46 PST 1998 >Originator: jason@idiom.com >Organization: >Release: 1.25b >Environment: Solaris2.6 & Linux2 >Description: As in the synopsis. This is insufficient resolution for sites with contractual obligations of response time, or any real timing tests. >How-To-Repeat: >Fix: pick up http://www.idiom.com/~jason/millisecond_timer.patch It adds a Rule that only turns on if mod_log_config is installed that changes the %T directive behaviour to log the seconds as %.3fs using gettimeofday instead of time(0); If the Rule is not in place, the old behaviour applies. %0 >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: dgaudet State-Changed-When: Wed Mar 18 10:20:45 PST 1998 State-Changed-Why: Thanks for the patch but it will be left in contrib for now. Timing things in the server is not really accurate at all for timing trials. The server has no idea when all the data has left its network buffers, and so the times are at best an approximation... so millisecond resolution isn't really much of a win. Dean Responsible-Changed-From-To: apache-contrib@apache.org Responsible-Changed-By: dgaudet Responsible-Changed-When: Wed Mar 18 10:20:45 PST 1998 Responsible-Changed-Why: mark as contrib %0 >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]