VPS CPU limits (vps gets shutdown by host).
I recently moved to an OpenVZ host listed on LowEndBox, moving a vps which we had running on a similarly spec Xen host for the last year with no problems at all. Both vps's are advertised as 512mb/1v-cpu. The reason we moved to the new host was for extra bandwidth.
The vps is used to run php/mysql based script which runs once a day and:
- reads our supplier websites for data (~2gb bandwidth)
- sorts the data into categories
- ftps the zipped up data to our live server.
Which takes anywhere from 3 - 5 hours to run. This was all set up fine, but after running for 1 week on our new host, we were shut down for excessive cpu use. Quoting the host:
"Keep in mind that you were using 10 E3-1240v2 cores with your VPS by itself."
Can anyone shed some light on how/why this is happening? I think it is because we switched to a OpenVZ container, which does not have the same resource limiting functionality. I admit our script does use a lot of CPU/Memory (1 mill records are being sorted), but if it takes 5 minutes or 5 hours, it doesn't matter, it just needs to happen once a day, as it was on our old host. My understanding is it shouldn't matter to our host what cpu/mem scripts we are running, as they should be limited to our VPS container.