ServerBear Performance Comparison of Rackspace, Digital Ocean, Linode and Vultr

scottalanmiller

Still waiting on RS.

scottalanmiller

Rackspace info is up.

IRJ

@scottalanmiller Is lower better?

dafyre

It is odd to see that DO has the lowest IO rate, but the ~~overall~~ second highest score.

Edit: Fixed typo.

travisdh1

@dafyre said:

It is odd to see that DO has the lowest IO rate, but the overall highest score.

IOPS it makes sense. Yes, write is slower, but read is crazy fast. Or do I have the read/write reversed? I'm used to seeing things listing read first

wirestyle22

Vultr with that NJ location. Hi handsome.

scottalanmiller

@IRJ said:

@scottalanmiller Is lower better?

Lower what exactly?

scottalanmiller

@travisdh1 said:

@dafyre said:

It is odd to see that DO has the lowest IO rate, but the overall highest score.

IOPS it makes sense. Yes, write is slower, but read is crazy fast. Or do I have the read/write reversed? I'm used to seeing things listing read first

I wrote the header backwards.

IRJ

@scottalanmiller said:

@IRJ said:

@scottalanmiller Is lower better?

Lower what exactly?

bench

scottalanmiller

@IRJ said:

@scottalanmiller said:

@IRJ said:

@scottalanmiller Is lower better?

Lower what exactly?

bench

Higher is better. I think that IOPS are a small amount, if any, of that score. It's about computational performance.

wirestyle22

@scottalanmiller said:

We need some latency numbers from around the world. Anyone want to collect some for us?

Here is the first IP address. A long running ping (hundreds or thousands of pings) would be good, we need the final stats from that:

104.236.119.59

108.61.151.173

172.99.75.133

We have a good idea on bandwidth, IO, CPU and memory. Network latency is pretty huge.

104.236.119.59 = 8 MS Average 1,000 pings
108.61.151.173 = 7 MS Average 1,000 pings
Mangolassi.it (162.242.243.171) = 14 MS average 500 pings

scottalanmiller

Whoops, sorry. We just killed the RS node because it is expensive

You can test that RS ping against mangolassi.it instead. Same location, same node type. Sorry.

dafyre

@scottalanmiller said:

Whoops, sorry. We just killed the RS node because it is expensive

You can test that RS ping against mangolassi.it instead. Same location, same node type. Sorry.

With the RS nodes being so expensive... why would you not stand them up on DO or Vultr?

Edit: I mean for production and not tests like this.

wirestyle22

@scottalanmiller said:

Whoops, sorry. We just killed the RS node because it is expensive

You can test that RS ping against mangolassi.it instead. Same location, same node type. Sorry.

Running now. Will update my above post.

scottalanmiller

@dafyre said:

@scottalanmiller said:

Whoops, sorry. We just killed the RS node because it is expensive

You can test that RS ping against mangolassi.it instead. Same location, same node type. Sorry.

With the RS nodes being so expensive... why would you not stand them up on DO or Vultr?

Edit: I mean for production and not tests like this.

Well DO and Vultr were not well known or well tested at the time that most of the RS nodes were created. And RS still offers a lot of features that those do not, like load balancers. But these days, the advantages to RS are fewer and fewer.

scottalanmiller

@wirestyle22 said:

@scottalanmiller said:

Whoops, sorry. We just killed the RS node because it is expensive

You can test that RS ping against mangolassi.it instead. Same location, same node type. Sorry.

Running now

Thanks

scottalanmiller

Right now, we are favouring a migration to Vultr. But the Linode test is running and is a major contender. Information on that to follow....

wirestyle22

updated above

brianlittlejohn

Ping statistics for 108.61.151.173:
Packets: Sent = 204, Received = 203, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 62ms, Average = 58ms

Ping statistics for 104.236.119.59:
Packets: Sent = 231, Received = 229, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 66ms, Average = 56ms

Ping statistics for 162.242.243.171:
Packets: Sent = 95, Received = 94, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 56ms, Average = 51ms

About the same from west Texas.

scottalanmiller

OMG WE HAVE A WINNER!!!!

Linode just took everyone out back and took their lunch money!! They have load balancers too!! (a la Rackspace and Amazone.) Look at that IO capacity!!! And that UNIX Bench! Their single thread was by far the fastest too!