Are we not warned if by Lunarpages admins monitoring shared servers if we are causing issues with server load, processes, or memory, allowing us to take action to disable the consistently offending apps/content? Do the Lunarpages admins just move the site to the non-production server without warning or suspend it without warning? The last thing I need is to have the four fantasy baseball leagues I host via my account to have their seasons disrupted because I did not have the opportunity to take action upon the advice of Lunarpages admins. I would have assumed Lunarpages admins would contact the customer if there was a problem via the same email account associated with the Lunarpages account (the one used for notifying us of an upcoming or processed hosting bill).
The only problem with checking the impact of AJAX Chat is that I really do not expect regular use of AJAX Chat beyond a few users a day. I could be wrong. But, it is not as if I expect all 50 users on concurrently ever let alone on a regular basis. Therefore, it will be hard to pick a day to ask support for an analysis of load, process, and memory use. I am concerned that if I request forum users test out the chat application at a given time then it will trigger a Lunarpages admin reaction of pushing the site to a non-production server or suspending it.
Think of it this way, if you are causing load so that all other accounts have sluggish or non-working sites due to your application, then what choice do we have? We do not normally notice an account to see it is high usage until that account starts causing actual issues on the server. If the site only does it for a short period of time such as 5-10 minutes, we would not take any action, since it would have ceased after a very short time to be an issue. If the issue continues after 5-10 minutes and does not stop causing load or high memory or processes, we cannot allow the account to continue causing the load and we do not have pre-warning either that it will be until it happens.
Imagine our quandary if we were to warn you rather than take action when your account is causing high load (or even possibly coming close to crashing the server) and we had to wait until you fixed the issue, causing slowdown and site unavailability for every other person on that server. We cannot do that. Moving a customer to non-production servers really does not negatively impact the site as it would still be up and the non-production servers are typically beefier to handle high resource usage over the regular production ones. The reason they are called non-production is that an account can only remain on that server for around a month without doing anything to improve resources before we ask the site owner to either upgrade to VPS or dedicated or ask the owner to find other hosting.
We rarely suspend sites rather than move them. The main instances when a site is suspended would be it is huge (10 or more GB large) and would take forever to move it over, causing downtime for the user if we tried anyway and possibly not copying everything. Another instance would be when the site is getting attacked by a denial of service (DoS) and moving the account won't fix the issue. The final instance would be when an account is exploited and we are unable to locate the exploited script(s), so we have no choice but to suspend until the customer can go over the account to find the exploit.
We don't take actions on an account unless we absolutely must do so, since we really have no desire to upset a paying customer, but if that paying customer is negatively impacting all the other paying customers on the shared server, then we do what is necessary to get that account off the server onto non-production to improve the usage on the production server. If we did not do this, then your account would suffer when another user is high usage and we allow that user to make the choice after slowing down the machine or crashing it on when to take action by warning the user. Everyone wants the server to respond quickly and work. You are benefited as a normal user who isn't high usage when we move high usage users off your server, and you are benefited as a high usage user who is impacting everyone else when we move your account to non-production, since we didn't suspend you and did allow you to fix it. How would you be benefited in any fashion if we warned high usage users before moving them? First, if we did that, your site would be slow due to that user until they fixed their usage. Second, if we did that, your site would be slow if you were the high usage account until you fixed your usage, since your site would be slowing down the server for your account along with every other account.
I hope this clarifies the reasoning for you on what happens.
