Live data from Hacker News

Benchmarking AWS, DigitalOcean, Linode, Packet, and Vultr

goldfirestudios.com

11–17 of 17 posts

Re: Benchmarking AWS, DigitalOcean, Linode, Packet, and Vultr

#13
I used to use DO, but switched off after they decided to disconnect my droplet for 3 hours when it got DDoS'd. It didn't matter that my node was able to handle the traffic. I was only using it for a Mumble VOIP server and an IRC bouncer, so it's not like I was going to lose money by having some business going offline, but still frustrating and enough to decide that should I ever need to run an actual business, I definitely won't use DO for it.

Re: Benchmarking AWS, DigitalOcean, Linode, Packet, and Vultr

#14
Rubbish. Why is there even a section describing its methodology when it's comparing $40 and $50 instances against $20 ones? I can see why they might compare the $62 EC2 instances against other vendors' cheaper ones as that is the point of their investigation, but the challengers should be on a level playing field. Seems to me that they wanted DO to 'win'.

Re: Benchmarking AWS, DigitalOcean, Linode, Packet, and Vultr

#15

Rubbish. Why is there even a section describing its methodology when it's comparing $40 and $50 instances against $20 ones? I can see why they might compare the $62 EC2 instances against other vendors' cheaper ones as that is the point of their investigation, but the challengers should be on a level playing field. Seems to me that they wanted DO to 'win'.

If you would read the paragraph directly after the list of instances tested you would see this was directly addressed. This test wasn't meant to mislead and was simply exploring the best options for us. This isn't the same for everyone, which is why we open-sourced the tool we made so that you can run your own tests as well.

Re: Benchmarking AWS, DigitalOcean, Linode, Packet, and Vultr

#16
post #6

I think the AWS failures on iops tests should've been examined more prior to publication, or at least explained more to the reader. AWS General Purpose EBS volumes scale based on volume size, so a purely naively-done test with a default AMI's performance could be as low as 24 iops (8GB*3 IOPS per GB) once exhausting it's burst iops quota. I think it's unfair to compare apples to oranges here, as you can make these vo…

The point of this test wasn't to determine the absolute limits. It was to determine what the actual real-world performance would be on the instances/servers we would actually be using.

Re: Benchmarking AWS, DigitalOcean, Linode, Packet, and Vultr

#17
post #15

Rubbish. Why is there even a section describing its methodology when it's comparing $40 and $50 instances against $20 ones? I can see why they might compare the $62 EC2 instances against other vendors' cheaper ones as that is the point of their investigation, but the challengers should be on a level playing field. Seems to me that they wanted DO to 'win'.

If you would read the paragraph directly after the list of instances tested you would see this was directly addressed. This test wasn't meant to mislead and was simply exploring the best options for us. This isn't the same for everyone, which is why we open-sourced the tool we made so that you can run your own tests as well.

> Even though neither Linode nor Vultr offer a CPU optimized tier, we wanted to test the options we would actually be using if we went with each provider.

This is the part that doesn't make sense. They basically chose one type from each vendor, before benchmarking. If there are clearly instance types at twice the cost and still lower than types from other vendors, the results were stacked. How can you see this any other way?

Post reply on HN