Also, I'd like to understand this:
>the advantage is probably going to be the predictable latency since it (almost) all runs on bare metal.
Surely you get a VM don't you? How can it run on bare metal while giving you full access to your image? What did you mean by this bare metal remark . . . Thanks!
[1] https://www.google.com/search?q=1+month+in+seconds
[2] https://www.google.com/search?q=136+mb%2Fsecond+*+1+month
Almost exactly 8 times, as a matter of fact :)
I use Mb/s for megabits/s and not megabytes, so that comes out to a bit more than 40TiB, 20 up and 20 down.
(The 136Mb/s I estimated was a big too high, actually. Here is my bandwidth chart if you're interested: https://i.imgur.com/l1rCeHC.png)
>Surely you get a VM don't you? How can it run on bare metal while giving you full access to your image? What did you mean by this bare metal remark . . . Thanks!
I believe they have their own custom hardware that they manage directly, they spin one up and you run bare metal on one of these with some local SSDs attached. With the exception of, I think, the VPS which is KVM.
Do you run a web server on yours? Can you check locally what your actual latency is for curl-ing (or wgeting) a page? I mean the actual timestamp difference from your local machine, such as your laptop or desktop. I don't intend to have a lot of traffic but I really, really hate latency. thanks for all this info btw.
Hope that helps.
The CPU on the other hand isn't the beefiest (there are comparative benchmarks floating around), the advantage is probably going to be the predictable latency since it (almost) all runs on bare metal.