Req #50652 [Ana->Sus]: time call optimization

From: Date: Wed, 21 Oct 2020 10:44:11 +0000
Subject: Req #50652 [Ana->Sus]: time call optimization
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-229838@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=50652&edit=1

 ID:                 50652
 Updated by:         cmb@php.net
 Reported by:        robert_xp at gmx dot net
 Summary:            time call optimization
-Status:             Analyzed
+Status:             Suspended
 Type:               Feature/Change Request
 Package:            Date/time related
 Operating System:   *
 PHP Version:        5.3.1
 Block user comment: N
 Private report:     N

 New Comment:

Apparently, there would be the need to discuss the details of this
feature request, for what this bug tracker is hardly suitable.
Therefore, please forward the request to the PHP internals mailing
list[1].  For the time being, I'm suspending this ticket.

[1] <https://www.php.net/mailing-lists.php#internals>


Previous Comments:
------------------------------------------------------------------------
[2010-01-04 21:00:15] rasmus@php.net

I'm not completely against this one.  At Yahoo we replaced the 
expensive gettimeofday syscalls with a fast system-wide replacement so 
it wasn't just PHP that benefitted.  They are not insignificant and 
since the bulk of scripts do run as quick web requests where it is 
perfectly fine for all time calls to get the request timestamp, and 
sometimes it even fixes edge-case bugs when they do, so the idea of 
having some sort switch to enable this optimization is not bad.  We 
would probably have to keep the default as it is though to avoid any BC 
breaks.

------------------------------------------------------------------------
[2010-01-04 15:11:49] robert_xp at gmx dot net

Yes, that's right. I think this is the only point, that speaks really against this solution but
most scripts should be executed in < 0.x sec and calling time(NULL) many times can be optimized
this way.

A good improvement could be, applying the patch and change the SAPI handling to check against a
config variable if a optimized time handling should be used - with default using the old approach.

------------------------------------------------------------------------
[2010-01-04 12:25:31] derick@php.net

We can't do this, as for longer running scripts the value as returned by time() can change
(like once every second).

------------------------------------------------------------------------
[2010-01-04 12:18:06] robert_xp at gmx dot net

Description:
------------
Sure, it is not so critical to patch this but you use ever time(NULL) to get the current time in
most functions. There is a better way going over the SAPI interface and retrieve a cached value. I
published also a patch for all time(NULL/0) calls on http://www.xarg.org/2009/12/php-hacking/

I also hacked the FCGI sapi to get the time value direclty from the webserver - yes it is not
supported by default.



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=50652&edit=1


Thread (7 messages)

« previous php.bugs (#229838) next »