All The Suspensions..

[infopage]

I got many suspension notices such as: " You have been suspended for high system resource usage. Accounts are suspended for usage when they are detected to have consistently high cpu usage, memory usage, and process amounts" ... yet I am barely using system resource according to the pie chart you have displayed in this control panel. I firmly believe this is due to the fact I have a wordpress blog which requires me to log in to post and occasionally modify settings therein and due to the logging in, your systems registers this as "high process amounts" but in no way means I actually have a high cpu usage . Please look into this and verify because the suspensions are annoying my site visitors making them think the site is not available.

[Smith6612]

Do you have any plug-ins installed onto Wordpress? Wordpress itself can be a pig, but the add-ons depending on how they are made can eat up a significant amount of resources too. Pay particularly close to any AJAX plug-ins. They can use up resources rather quickly.

[descalzo]

I got many suspension notices such as: " You have been suspended for high system resource usage. Accounts are suspended for usage when they are detected to have consistently high cpu usage, memory usage, and process amounts" ... yet I am barely using system resource according to the pie chart you have displayed in this control panel.

The pie charts show bandwidth and file usage. They do not show cpu usage or script memory usage (RAM).

It seems that the main culprit for such suspensions are WordPress blogs with plugins. If the plugin has to rewrite every URL in your blog or recreate a sitemap, that is a lot of computing going on (much of it is in database requests). Most of the plugin writers seem to assume that you are on a server by yourself, not sharing it with 10,000 other sites.

[infopage]

The pie charts show bandwidth and file usage. They do not show cpu usage or script memory usage (RAM).

It seems that the main culprit for such suspensions are WordPress blogs with plugins. If the plugin has to rewrite every URL in your blog or recreate a sitemap, that is a lot of computing going on (much of it is in database requests). Most of the plugin writers seem to assume that you are on a server by yourself, not sharing it with 10,000 other sites.

This does make a bit of sense ... so I guess now my question is if I upgrade to the Static Premium hosting solution or the Hosting Upgrade solution will I still get these suspensions??

[Livewire]

This does make a bit of sense ... so I guess now my question is if I upgrade to the Static Premium hosting solution will I still get these suspensions??

Depending on what is going sideways and using up too much, it's possible you could.

That said, paid's got higher limits:



* May not use more than 50% of available CPU resources for more than 120 seconds at a time.
* May not use more than 50% of available CPU resources for more than 5 minutes out of a 60 minute period.
* May not use more than 820MB of memory combined between processes
* May not have more than 10 processes running at any given time.

If you trip past any of those it'll still suspend, but that said it'd be a lot more difficult. Here's frees:

* 25% CPU
* 5% memory (eg 400 MB)
* 240 seconds of CPU time per hour
* 20 concurrent processes executing


Edit: You added the Hosting Upgrade Solution question while I was posting; that one will still cause suspensions because you stay on the free servers. The upgrade to premium static moves you to paid.

[descalzo]

This is from the log, one process using 86% of one CPU, there's more entries like this one in the log file as well.

From Anna, in another thread. That was a RSS feed script that a bot was slurping.

[infopage]

From Anna, in another thread. That was a RSS feed script that a bot was slurping.

..I deleted that particular file where that script was located and still got suspended overnight

[infopage]

Depending on what is going sideways and using up too much, it's possible you could.

That said, paid's got higher limits:



* May not use more than 50% of available CPU resources for more than 120 seconds at a time.
* May not use more than 50% of available CPU resources for more than 5 minutes out of a 60 minute period.
* May not use more than 820MB of memory combined between processes
* May not have more than 10 processes running at any given time.

If you trip past any of those it'll still suspend, but that said it'd be a lot more difficult. Here's frees:

* 25% CPU
* 5% memory (eg 400 MB)
* 240 seconds of CPU time per hour
* 20 concurrent processes executing


Edit: You added the Hosting Upgrade Solution question while I was posting; that one will still cause suspensions because you stay on the free servers. The upgrade to premium static moves you to paid.

The part of your response that I bold-marked may be the part that gets me considering your other remark regarding the WP plugin processes

[Livewire]

The part of your response that I bold-marked may be the part that gets me considering your other remark regarding the WP plugin processes

What was my other remark? I went back in my post history but the only one I can find was askign what the active plugins were; as far as I know all the plugins execute under one php process - the one loading the pages.

That said I know it's limited to 10 on paid and 20 on free, but with the decrease in users (and the hardware stays the same), the stuff executes that much quicker as well - that tends to mean there's not an issue with 10 concurrent processes running unless something's broke bad

[infopage]

What was my other remark? I went back in my post history but the only one I can find was askign what the active plugins were; as far as I know all the plugins execute under one php process - the one loading the pages.

That said I know it's limited to 10 on paid and 20 on free, but with the decrease in users (and the hardware stays the same), the stuff executes that much quicker as well - that tends to mean there's not an issue with 10 concurrent processes running unless something's broke bad

My bad, I was actually referring to descalzo's prior remark:

t seems that the main culprit for such suspensions are WordPress blogs with plugins. If the plugin has to rewrite every URL in your blog or recreate a sitemap, that is a lot of computing going on (much of it is in database requests).

...but you did give me some seriously positive facts to consider