Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11968
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 37380 invoked by uid 1010); 6 Aug 2004 16:00:28 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 37315 invoked by uid 1007); 6 Aug 2004 16:00:28 -0000
Message-ID: <20040806160028.37314.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <5.1.0.14.2.20040724003444.034ea690@127.0.0.1> <5.1.0.14.2.20040724003444.034ea690@127.0.0.1> <5.1.0.14.2.20040725104701.02789d40@127.0.0.1> <Pine.WNT.4.56.0408060801470.4040@DELL>
Date: Fri, 6 Aug 2004 08:59:29 -0700
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Posted-By: 64.142.6.231
Subject: Re: [PHP-DEV] Everyone on the road?
From: pollita@php.net ("Sara Golemon")

> I meant to mention this a while ago, but it slipped my mind.  Most web
> servers do that time() call for us at the beginning of the request because
> they need it for logging purposes.  I think the right approach here is to
> add a SAPI call to expose this.  For Apache-1.3 it is right in the
> request_rec in the request_time field.  Obviously the SAPI call would
> simply do the time() call itself if it can't fetch it from somewhere
> internally.
>
It sounds good enough, but I'd worry about people using this in
incompletely-thought-out benchmarking scripts.

A SAPI which supports the request time record would appear to take slightly
longer than a SAPI which does not (the time between processing the request
in the web server and passing off to PHP {plus compile, plus execute down to
that instructuion})

<note>
  Do <emphasis>NOT</emphasis> use this method for benchmarking between
different webservers, inconsistent implementations could give unexpected
results.
</note>

-Sara