max execution time

[Anon]

a few of my once a day caching and logging scripts takes around 10 seconds to execute now, and i have my max execution time at 30 seconds. forseeing that server load and other factors might take those scripts over 30 seconds to run, i would like to increase the max value to 2 minutes.

what are the downsides of such a change on a heavily loaded server?

[ame12]

I don't think there's any downside if you just run these batch scripts a few times a day. If the remainder of your site (called by users) doesn't need the extra execution time, then it won't be used. Those settings are really there to let you control how much time and memory (worst-case) you'll need. If your other scripts are well-behaved, it should have no impact IMO.

Dave

===========================================
http://badblue.com/helpphp.htm
Free small footprint web server for Windows

PHP, P2P file-sharing, transcoding and more

[[deleted]]

But...
If that script uses MySQL, that script can keep the tables it works with locked for the duration of the script, locking other users out.
This can snowball into scripts waiting for scripts waiting for scripts...

At the current 10 seconds it shouldn't be a problem, but if it gets longer it could be...

[mattee]

with maintenance scripts like that which take a long time to execute I set my max execution time to "0" which means there is no time out.

That stuff gets run by cron at 3 or 4 am and I don't worry about it at all.

If you're running linux and apache don't worry about it. I'm unable to notice a degredation when any of these scripts are running.