I must admit Linode IO is pretty bad, :~# dd if=/dev/zero of=test bs=64k count=3...

gingerlime · on March 19, 2013

    London 512:
    201326592 bytes (201 MB) copied, 4.93267 s, 40.8 MB/s
    201326592 bytes (201 MB) copied, 5.89248 s, 34.2 MB/s
    201326592 bytes (201 MB) copied, 5.97411 s, 33.7 MB/s

    London 2048:
    201326592 bytes (201 MB) copied, 4.50047 s, 44.7 MB/s
    201326592 bytes (201 MB) copied, 2.90073 s, 69.4 MB/s
    201326592 bytes (201 MB) copied, 3.30499 s, 60.9 MB/s

    another London 2048:
    201326592 bytes (201 MB) copied, 3.16025 s, 63.7 MB/s
    201326592 bytes (201 MB) copied, 2.86327 s, 70.3 MB/s
    201326592 bytes (201 MB) copied, 4.0267 s, 50.0 MB/s

    Newark 4096:
    201326592 bytes (201 MB) copied, 3.19571 s, 63.0 MB/s
    201326592 bytes (201 MB) copied, 4.17497 s, 48.2 MB/s
    201326592 bytes (201 MB) copied, 4.60173 s, 43.8 MB/s

    Atlanta 4096:
    201326592 bytes (201 MB) copied, 2.19477 s, 91.7 MB/s
    201326592 bytes (201 MB) copied, 2.63818 s, 76.3 MB/s
    201326592 bytes (201 MB) copied, 3.04094 s, 66.2 MB/s

    Dallas 2048:
    201326592 bytes (201 MB) copied, 2.65925 s, 75.7 MB/s
    201326592 bytes (201 MB) copied, 3.11197 s, 64.7 MB/s
    201326592 bytes (201 MB) copied, 3.45745 s, 58.2 MB/s

corford · on March 19, 2013

Another 512 data point (London DC, all 5 tests run within a ~30 second window):

201326592 bytes (201 MB) copied, 2.61587 s, 77.0 MB/s

201326592 bytes (201 MB) copied, 3.06237 s, 65.7 MB/s

201326592 bytes (201 MB) copied, 5.70759 s, 35.3 MB/s

201326592 bytes (201 MB) copied, 6.24756 s, 32.2 MB/s

201326592 bytes (201 MB) copied, 3.98084 s, 50.6 MB/s

EDIT:

For comparison, here's the same test on a 4GB DO instance (Amsterdam DC):

201326592 bytes (201 MB) copied, 6.16116 s, 32.7 MB/s

201326592 bytes (201 MB) copied, 5.08132 s, 39.6 MB/s

201326592 bytes (201 MB) copied, 7.73071 s, 26.0 MB/s

201326592 bytes (201 MB) copied, 7.55657 s, 26.6 MB/s

201326592 bytes (201 MB) copied, 7.9936 s, 25.2 MB/s

edam · on March 19, 2013

Linode512:

    201326592 bytes (201 MB) copied, 3.11716 s, 64.6 MB/s
    201326592 bytes (201 MB) copied, 2.70099 s, 74.5 MB/s
    201326592 bytes (201 MB) copied, 3.28993 s, 61.2 MB/s
    201326592 bytes (201 MB) copied, 2.98622 s, 67.4 MB/s
    201326592 bytes (201 MB) copied, 2.93612 s, 68.6 MB/s

csomar · on March 19, 2013

Tried with 4 tests (512Mb instance) and I got quite different results (though nothing like 4.9 MB/s)

201326592 bytes (201 MB) copied, 4.08309 s, 49.3 MB/s

201326592 bytes (201 MB) copied, 5.22498 s, 38.5 MB/s

201326592 bytes (201 MB) copied, 5.85255 s, 34.4 MB/s

201326592 bytes (201 MB) copied, 2.94301 s, 68.4 MB/s

jebblue · on March 19, 2013

Here's what I got:

<code> 3072+0 records in 3072+0 records out 201326592 bytes (201 MB) copied, 5.52118 s, 36.5 MB/s </code>

andyhmltn · on March 19, 2013

That's pretty slow. I get this:

3072+0 records in 3072+0 records out 201326592 bytes (201 MB) copied, 2.31272 s, 87.1 MB/s

agildehaus · on March 19, 2013

On my 512MB Linode, repeating this command 10 times:

74.5, 70.5, 55.4, 56.1, 84.8, 75.1, 73.7, 58.0, 67.5, 61.8

Average of 67.7 MB/s

Dallas

RKearney · on March 19, 2013

I got this

  201326592 bytes (201 MB) copied, 3.05352 s, 65.9 MB/s

Atlanta, GA

zxer · on March 18, 2013

another datapoint:

Linode 512: 3.96647 s, 50.8 MB/s

DigitalOcean 512: 5.87315 s, 34.3 MB/s

(though the digitalocean one feels much snappier)

derengel · on March 19, 2013

wow, in what DC is your linode on?

zxer · on March 19, 2013

London