that's not really relevant -- no customers are really allowed to use a VPS as if it were bare-metal.
This is a pretty routine issue for people (myself included) who have mistakenly considered using a few temporarily spun droplets for a few hours of intense number crunching.
The 'nicest' complaint I've received was from Linode, which was less of a complaint a more of a warning like 'Do you know what your VPS is doing?' rather than 'Don't do this with your VPS.'. They never really told me to stop -- just wanted to make sure that it was intentional.
> no customers are really allowed to use a VPS as if it were bare-metal
I don't agree. What I'm paying for are vCPUs not actual CPUs. So I know I'm not getting bare metal and that the compute power is already managed by VPS provider.
Are you saying that on top of that I also have to monitor and be responsible my own CPU usage or risk getting banned?
What are the rules?
That's why I wouldn't do anything serious on DO, just use it for low-cost side projects.
AWS has explicit CPU credits on their cheaper instances. They built their system to allow bursts of activity. If Digital Ocean doesn't have that their offering is simply weak.
Also I recall few years ago Digital Ocean send me a message that referenced specific processes running on my VM. I know that they have access to that if they want to but looking into specific processes was stepping over the line in my book.
I moved my servers from Digital Ocean shortly after that.
That's enough for me to never use DO again. One pays for a server but then using it is fraudulent?!