URGENT: too much CPU and memory usage after upgrade

[dealbyethan.com]

Hi,

After upgrading to zen cart v1.3.9c recently, our hosting company just informed us that because we are using too much system CPU and Memory resources, they were forced to disable web access to our account. This doesn't make sense because our traffic is going down recently due to the upgrade.

Here is a summary of the CPU and memory usage on our account over the past 24 hours:

CPU: 18.05 %
MEM: 0.72%

They believe the processes shown below are responsible for this level of resource usage.
-------------------
9414 12.5 0.2 41476 18600 ? S 07:21 0:00
/index.php
9418 12.0 0.2 41844 19008 ? D 07:21 0:00
/index.php
9428 15.3 0.2 41744 18616 ? S 07:21 0:00
/index.php
-------------------
Top Process %CPU 89.7 /index.php
Top Process %CPU 75.1 /index.php
Top Process %CPU 62.0 /index.php
-------------------

Please help. We are very worried.

[Website Rob]

There are many reasons why the load could be so high and you might want to try the Query Cache module as it has proven to bring resource usage down. Not sure though if it works with 1.3.9c.

[dealbyethan.com]

Hi,

Installed Query Cache but it didn't help much. Our hosting still said our site is using excessive resources. Please help.

[Protostack]

How did you go with this? I'm running 1.3.9f and am experiencing the same problem. Like yourself I tried the query cache but it didn't help much.

Daniel.

[igrossiter]

i had the same problem, and i solved by turning off the debug module, check the file in includes>extra_configures>enable_error_logging.php(delete or rename it)
it was creating thousands of files because of some waring errors.

[DrByte]

er, um, well ... the FIRST thing you should be doing is FIXING those errors that it was reporting.

Merely turning off the reporting is NOT fixing your REAL problem: you're basically sticking your head in the sand hoping the problems will go away just because you can't see them.

[igrossiter]

yes of course ^^'

[Protostack]

In my case there were errors, but they were caused by the query cache addon. I've fixed them now but still high CPU utilisation.

[dealbyethan.com]

Query cache is not made for v1.3.9. Therefore it might generate some errors. DrByte is right, you need to fix your current problems. The cache and error logs will give you some ideas.

[template140]

I have the same problem.. it's very strange, i don't know how to fix it