Comments on: GoDaddy: undocumented 20-second CPU time maximal execution limit? (python, ELF, etc)

By: Sid

Sid — Sun, 19 Oct 2008 13:55:59 +0000

Ah, I did not realise the difference.
I’m on GoDaddy right now, and my scripts seem to be running fairly well, and Wordpress 2.6 with decent speed, although I noticed that the Deluxe plan had better performance than my Economy hosting plan, although this might have been a placebo.
Anyways,
Cheers,
Sid

By: Bogdan

Bogdan — Sun, 19 Oct 2008 08:46:18 +0000

Sid,

that won’t show anything, as “sleeping” doesn’t consume CPU time as actively as an infinite loop - so this just is not the CPU time you would be trying to measure with this PHP script.

Moreover, as my little experiment with an infinite loop did work, there is no need in any additional testing.

By: Sid

Sid — Sun, 19 Oct 2008 05:01:04 +0000

I guess you could probably try this out with a PHP script which has code like below:

sleep(10);
echo ‘The script has been running for 10 seconds’;
sleep(10);
echo ‘the script has been running for 20 seconds’;
sleep(10);
echo ‘the script has been running for 30 seconds’;

Etcetera? Not sure, just an idea.
Cheers,
Sid

By: An alternative to shared hosting » Autarchy of the Private Cave

An alternative to shared hosting » Autarchy of the Private Cave — Wed, 04 Jun 2008 16:51:44 +0000

[...] it’s better to have a 125MHz-clamp on CPU, than have a 20-seconds maximal CPU time limit [...]

By: GoDaddy shared hosting: too slow? » Autarchy of the Private Cave

GoDaddy shared hosting: too slow? » Autarchy of the Private Cave — Fri, 19 Oct 2007 14:18:13 +0000

[...] GoDaddy: undocumented 20-second CPU time maximal execution limit? (python, ELF, etc) [...]