3 ms·
>I don't understand your numbers. 1 month in seconds is 2,629,743 seconds [1] and at 136 MB/s that is 357 TiB [2] - almost 10 times what you quoted Almost exac
by tux3 10y ago
>I don't understand your numbers. 1 month in seconds is 2,629,743 seconds [1] and at 136 MB/s that is 357 TiB [2] - almost 10 times what you quoted
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 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.
- logicallee 10y agoThanks. Right, I just let Google do the conversion (per my footnotes) and didn't think about the bit/byte thing - ooops. 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.
- tux3 10y agoNo problem! I checked with an apache2 instance on a VC1S in Paris, my ping to it is 25ms and curl from my laptop takes about 90ms. Hope that helps.
- logicallee 10y agoYes! This is useful. Thank you :)