Over Usage of resources

[amresh_rai47]

Hello,

My site is suspended because of over usage of resources. I am using a small wordpress blog, not sure how I have exceeded the limits?
Can you please tell is your resource usage policy? It seems to be on hourly basis. Kindly explain. Not getting much idea about resource usage from options available in cPanel.

Also is there any way we would come to know if my domain is suspended because of over usage of resources? Are you guys sending email alert for the same or simply disabling the domain ?

---------- Post added at 08:00 AM ---------- Previous post was at 07:56 AM ----------

Instead of performing the resource usage calculation on hourly basis, can't you perform this on daily basis? Because we are not working with the site for the whole day. Making any modification/changes to the site might increase the resource usage for that specific hour but the traffic will be negligible for the rest of the days.

Kindly consider this too.

[vv.bbcc19]

Instead of performing the resource usage calculation on hourly basis, can't you perform this on daily basis? Because we are not working with the site for the whole day. Making any modification/changes to the site might increase the resource usage for that specific hour but the traffic will be negligible for the rest of the days.

Kindly consider this too

Nice that you are suggesting.May be they will think again.But the decision which is taken on hourly check is a carefully thought decision.
The easier way is to check which plugins are causing you the problems.
Also as you are using wordpress, kindly follow this thread
Wordpress Plugins
where you can request a check on your favorite plugin.
Good Luck.

[amresh_rai47]

Thank you for your suggestion. Will have a look to the Plugin settings and will try to avoid the issue again.

Nice that you are suggesting.May be they will think again.But the decision which is taken on hourly check is a carefully thought decision.

I can understand how difficult it is to monitor the resource usage on a shared server and also the importance of this but if this can be changed on daily basis then that will be great

[essellar]

You've listed a couple of plugins that are known to be resource hogs --- and it doesn't matter how many people are using the site. All In One SEO and Google XML Sitemaps are both known to use a lot of resources. W3 Total Cache is great if you have your own server and can use all of the memory you want, but it's not so great on a shared server.

In short, you are using a lot more resources than your fair share. Please see the High Resource Usage wiki page for more information on how to get your site under control. Look for alternative plugins for some of your features; there are WordPress user boards that discuss plugins from a resource standpoint. This isn't the only site where WP plugins send users over their limits.

[amresh_rai47]

Thank you for your suggestion but I was under impression that WP Super Cache plugin is always useful even if we are on shared server because it will help us to minimise the resource usage by the site.

[essellar]

Cache just changes the kind of resources you use -- it trades disk access and database hits for RAM space, making your site more responsive (that is, you can handle more users because RAM is many times faster than disk or DB accesss). Unfortunately, RAM space and CPU time are the real limiting factors here and on most low-cost shared servers.

Let's say you're running on a physical box that has 64GB of RAM and 1000 user accounts (as an example) -- that leaves you with a "fair share" steady-state memory allotment of around 65MB. (Well, except that the server itself needs a chunk of memory for its own processes and daemons and and so forth, but let's keep it simple.) But you aren't running in a "steady state" -- everybody on the server, including you, has "burst" requirements, times when you need to use a lot of capacity for a short period of time (usually for less than a couple of seconds, but sometimes longer). A cache program says "I'll probably need to do that again soon" and holds the memory you've grabbed for a while before letting go.

This can actually be worse on a site with low activity since the cache needs to be rebuilt on almost every visit. Rebuilding the cache takes extra CPU time as well as memory space -- and you still need to make all of the database and disk requests that you would have had to make anyway.

Memcache is a great idea if you have a static memory allotment (dedicated server, VPS, "cloud instance" or a hard allotment on a shared server) and enough hits to justify the cache. It can work in a shared server environment if there are relatively few user accounts per server (definitely not the case here with free hosting accounts) and you can grab and hold a chunk of memory -- and you have enough hits to justify the cache. Heck, if you have a very dynamic site and a lot of users, you can use write-behind to update your actual database only during the slow moments. But if your site is relatively infrequently updated (less than several times a minute) and you don't have a static memory allotment, then there are other caching strategies that work a lot better (like rewriting your menus on update and storing them to create a single database hit on each user visit instead of computing them at service time, etc.).