Re: set_time_limit () - CPU time or elapsed time?
| From: | Tim Streater | Date: | Sun, 13 Apr 2014 09:51:00 +0000 |
| Subject: | Re: set_time_limit () - CPU time or elapsed time? | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-323183@lists.php.net to get a copy of this message | ||
On 13 Apr 2014 at 01:42, Stuart Dallas <stuart@3ft9.com> wrote:
>> I know that there is a note in the online doc for this function that says
>> that under windows, extra time such as database calls is included. Would that
>> include SQLite calls which wouldn't be included for the OS X version?
>
> * Under Windows it’s elapsed time spent executing the PHP script regardless
> of what it’s doing, but under other platforms it’s elapsed time spent
> executing PHP code only (so not including time spent executing other
> processes, running database queries, etc). So yes, time spent executing sqlite
> queries would only be included on Windows. If your queries are causing the
> order of magnitude difference in execution time your problem has nothing to do
> with PHP!
Mmmm. Then I may need to disable it altogether for Windows. Inter alia, the scripts communicate with
remote hosts, that may respond slowly, or have a lot to say. If all that time is going to be counted
against the script ...
Thanks.
--
Cheers -- Tim