Re: set_time_limit () - CPU time or elapsed time?
| From: | Tim Streater | Date: | Sat, 12 Apr 2014 20:45:00 +0000 |
| Subject: | Re: set_time_limit () - CPU time or elapsed time? | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-323181@lists.php.net to get a copy of this message | ||
On 12 Apr 2014 at 21:06, Jim Giner <jim.giner@albanyhandball.com> wrote:
> Having made some coding errors that put me in a loop or some other
> almost-endless process, I do believe that the time limit is cpu time.
> My host uses a default of 30 secs and I have chosen to reset my .ini
> file to be a 2 second default simply because that is quite a long time
> in processing terms and I don't want something to tick away for 30
> seconds of CPU time.
>
> If you have a user whose scripts (a user writing their own scripts) I'd
> say you might want to examine that logic. That - or you've got a hell
> of a lot of number crunching going on.
Perhaps I didn't make it clear that the user is running my app - and hence is running the
identical set of scripts that I'm running. I'm doing a fair bit with a number of SQLite
databases - perhaps I need to add an index.
--
Cheers -- Tim