The 200Mb/s unmetered pricing is really incredible.
I have a server moving 20+TiB up and 20+TiB down per month for 2.99€.
If I'm reading this right with EC2 pricing I'd be paying 1,750€/month just for the bandwith!
This comment actually got me to check them out, so right now I'm deploying 2 bare metal servers and benchmarking them against my DO boxen with interesting results. The SW boxen are outperforming the DO ones at times over 8x in disk IO, and connection to remote servers using vpsbench
Well, you're obviously costing them money. (I will say that I personally think it's a bit abusive of you - I mean 20 GB would be one thing, but "20+ TiB"... I mean it's like going to an all you can eat buffet and eating 70 whole lobsters. 7 is one thing - but 70?) At least you're giving them free press here. :)
On that note - how are latency and CPU access? Can you run a fast, performant site on it? (If you have actual numbers it would be great, such as ms to serve first page, for example, on an actual install.) Maybe some people here can help subsidize your excesses by hosting their tiny web apps on it... ;) (And knowing that if their site ever does blow up - suddenly spike in traffic - they'll be covered without huge bills.)
AWS and Google Cloud want people to think that, so that they can keep selling people McDonalds and charging Michelin prices for it.
Market-rate quality bandwidth is closer to $0.005-$0.015/GB. That's with peering to eyeball ISPs like Comcast and everything. Don't believe me, go to Voxility and crunch the numbers yourself.
Their marketing guys say about it what they're going to say. But under the hood, you tell me if you're getting something different:
Oh BTW, DigitalOcean's site just resolves to a Cloudflare controlled IP. If they can't successfully run their own servers on their own network, I won't either. You can have a different opinion here, but that's mine. I like to see my ISPs eating their own dog food.
That said, they are a business, and it's their job to make their bandwidth policies clear and enforce them. Either they're ok with a few users using tons of bandwidth or they can't be bothered to put in place a clear policy. Either way, it's not the user's problem.
How much bandwidth do you provide? What is the transfer limit?
Your server comes with between 200Mbit/s and 800Mbit/s
of internet bandwidth depending of your server. Checkout
the pricing page to find the exact value. The internal
bandwidth is only limited by the speed of your network card.
There is no transfer limit, transfer is unlimited.
That's the bandwidth policy. I've never had them crack down on me using the bandwidth I'm paying for, never heard anyone else say they've had a problem either
> I like to see my ISPs eating their own dog food.
I have to disagree in part here - No matter what is going on with the ISPs networking etc I want to be able to see status updates. Hosting off-network is great for this.
In DigitalOcean's case they can of course use multiple of their own regions I suppose, but if Cloudflare does the job the box is ticked for me
I would hope it's not abusive of me, I think I'm using around 136Mb/s of the promised 200. It's a Tor relay so it happily takes all the bandwidth it can get.
And I sure am happy to give them free press, it is pretty incredible :)
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.
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. Are you really averaging 136 Mb/s day-in, day-out?
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!
>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)
>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.
Thanks. 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.
I have a server moving 20+TiB up and 20+TiB down per month for 2.99€. If I'm reading this right with EC2 pricing I'd be paying 1,750€/month just for the bandwith!