Re: Re: Possible RFC: $_SERVER['REQUEST_TIME_FLOAT']
| From: | Rowan Tommins | Date: | Wed, 12 Apr 2023 14:04:28 +0000 |
| Subject: | Re: Re: Possible RFC: $_SERVER['REQUEST_TIME_FLOAT'] | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119957@lists.php.net to get a copy of this message | ||
On Wed, 12 Apr 2023 at 13:25, Herbert Groot Jebbink <
herbert@groot.jebbink.nl> wrote:
> fallback for REQUEST_TIME and REQUEST_TIME_FLOAT to hrtime seems not
> possible, hrtime is not based on the actual time, hrtime can be used to
> calculate a duration or so, not to retrieve the actual time itself.
>
Fair enough, but that makes my first question all the more important: are
there any situations or platforms where generating an hrtime value for
every request would have a performance penalty?
How does that performance (for everyone) compare with a single call to
microtime(true) in your application to calculate the duration from
REQUEST_TIME_FLOAT to start of profiling, with all subsequent profiling
using hrtime?
Regards,
--
Rowan Tommins
[IMSoP]