Enabling script now for some reason throws server load to 10-20+

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Enable thumb script on my site
2. watch server load go from 1 to 20-30 and higher

What is the expected output? What do you see instead?

I've had this script implemented for some time with no issues, now for some 
reason it maxes out my servers load immediately upon being added to my site (my 
site has been down since I can't run it without it currently)

What version of the product are you using? On what operating system?

1.16 on a quad core server with 8gb ram using centos 5.3

Please provide any additional information below.

I have had this script in use on my server for some time and my average hits 
per day hovers around 3k uniques/day, for some reason the script began acting 
up and causing the server to go to max load. I've put up a temporary index and 
everything is fine, I've disabled the script and everything is fine but my site 
doesn't work, the second I reenable the script the load shoots up so I know it 
is the cause.

I've applied all of the updates, set the max image limit to within defaults and 
have a completely capable server but no matter what I've tried I can't get it 
to comply. I'd really appreciate any input and/or advice because this site 
being down is costing me a bit of extra income.

Please let me know if you require any further information.

Original issue reported on code.google.com by prodigy...@gmail.com on 8 Nov 2010 at 4:54

[GoogleCodeExporter]

Is there no support happening here?

Original comment by prodigy...@gmail.com on 11 Nov 2010 at 4:13

[GoogleCodeExporter]

I am afraid this isn't a support forum, it's for reporting bugs - I do this as 
a hobby so only help when I have the time.

As for your problem, I am not sure I can help without more information. I don't 
know what has been added or changed that might have increased the server usage 
to the degree you are suggesting. For the script to change in the way you 
suggest something must have changed on the server. Have you updated the script? 
Changed directory permissions? Installed new software? Without knowing what has 
changed I can't really work out where the problems lie.

If you could go through the script and and make it die and then watch cpu usage 
you should be able to find where the problem lies. Add a die() command near the 
start of the script, and then slowly move it down the script until the cpu 
usage spikes. You will then know what the slow bit comes from.

Original comment by BinaryMoon on 21 Nov 2010 at 11:07

[GoogleCodeExporter]

I think I found the problem. Unfortunately I had committed the code with 
caching disabled. Stupid mistake and I apologise for that :S

Should all be fixed now

Original comment by BinaryMoon on 24 Nov 2010 at 2:09

• Changed state: Fixed