Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


DigitalOcean now offers double the memory and SSD on all plans :D - Page 19
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

DigitalOcean now offers double the memory and SSD on all plans :D

11415161719

Comments

  • @Nick_A

    1) They offer a no card free trial
    2) They willingly gave out a shit ton of free credit
    3) They're considerably larger than any LEB provider here - which makes it less of a risk

    That's it, nothing else to it. You can't blame anyone for trying them out either, I can definitely say that the performance is decent for the price.

  • I've used DigitalOcean, and their I/O and network speed was astronomically weak.

    If they're trying to reach Linode customers, that's fine. If they're trying to reach Amazon EC2 customers, this wins.

    I've used Linode before, and their networking and reliability is infinitely better than DO's. It has its limits, but it's a lot better IMHO.

    Being a RamNode customer makes both look weak.

    On to the VPS offered by DO (signed up with the ServerBear coupon and verified with PayPal):

    I/O speed was ~140MB/s. I've about the same, but a bit less with ChicagoVPS. My worst RamNode speed was ~230MB/s, so that department should get improved if it's really SSD.

    I've noticed a lot of SSH lag being my short time with them. I've had a lot better with Linode.

    Also, the way to open support tickets from them to you is strange. I didn't remember opening a ticket when they did, and I thought my account was hacked...

    tl;dr: digitalocean is even more horrible than linode, stay away

  • @PenguinManifesto said: digitalocean is even more horrible than linode, stay away

    But it's hard to say no when they keep giving you free credits!!

  • Linode also costs 4x more, quit comparing apples with oranges.

  • Not very impressed with performance.

    dd if=/dev/zero of=iotest bs=64k count=16k conv=fdatasync && rm -fr iotest

    16384+0 records in
    16384+0 records out
    1073741824 bytes (1.1 GB) copied, 30.2159 s, 35.5 MB/s

  • HalfEatenPieHalfEatenPie Veteran
    edited February 2013

    That 35.5 MB/s should be more than enough for most things.

  • But... come on?! What kind of SSD gets 35.5 MB/s under any type of load?

  • @flam316 said: But... come on?! What kind of SSD gets 35.5 MB/s under any type of load?

    Oh yeah forgot. They market it as SSDs.

    Yeah that's crap haha

  • @flam316 said: But... come on?! What kind of SSD gets 35.5 MB/s under any type of load?

    Open a ticket. That is not right.

    I get 250-400 for all my droplets with 3000+ iops. Which is way more than enough and awesome for $5.

  • @luma said: I get 250-400 for all my droplets with 3000+ iops. Which is way more than enough and awesome for $5.

    do you get that with your US droplet?

  • But... come on?! What kind of SSD gets 35.5 MB/s under any type of load?

    ...Any type of SSD under load?

  • rm_rm_ IPv6 Advocate, Veteran
    edited February 2013

    @KernelSanders said: Any type of SSD under load?

    But but but SSDs are magic, and you should get 1600+ MB/sec just by them being SSDs! :D

    @luma said: Open a ticket.

    I would simply not bother, make a snapshot, then destroy your droplet and make a new one. (Or better, make a new one, then destroy the old one).

    @Wintereise said: Linode also costs 4x more, quit comparing apples with oranges.

    A lot of people are switching from apples to oranges (or which one was Linode in your analogy? anyways, from Linode to DO), so nothing wrong with comparing their nutritional value.

  • All my nodes with DO get ~200MB/s. (US region)
    The thing I am not satisfied with DO is the response time of tickets.
    It seems they don't have staff on call 24*7.
    Sometime I don't get a response until 5~8 hours later.

  • All of my nodes with DO get ~200MB/s. (US region)
    The thing I am not satisfied with DO is the response time of tickets.
    It seems they don't have staff on call 24*7.
    Sometime I don't get a response until 5~8 hours later.

  • chinmoychinmoy Member
    edited February 2013

    @webflier said: The thing I am not satisfied with DO is the response time of tickets.

    It seems they don't have staff on call 24*7.
    Sometime I don't get a response until 5~8 hours later.

    Nearly all of my tickets have been answered in less that 30 mins. For the price, you shouldn't be expecting 24/7 support. You don't even get that with AWS unless you pay a buttload of money.

  • @chinmoy said: Nearly all of tickets have been answered in less that 30 mins. For the price you paying you shouldn't be expecting 24/7 support. You don't even get that with AWS unless you pay a buttload of money.

    That is why I am still with DO. :)

  • They are doing a good job...

    But one thing I didn't understand is .. why they removed a blog post which explained their minor downtime last month..

  • heiskaheiska Member
    edited February 2013

    @flam316 said: Not very impressed with performance.

    I used to be on a shitty node too, but then I created a new droplet from an image and this is what I've seen for the past two weeks (on AMS 1):

    dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
    16384+0 records in
    16384+0 records out
    1073741824 bytes (1.1 GB) copied, 2.41445 s, 445 MB/s
    ioping -c10 /
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=1 time=0.3 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=2 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=3 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=4 time=0.3 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=5 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=6 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=7 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=8 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=9 time=0.4 ms
    4096 bytes from / (ext4 /dev/disk/by-label/DOROOT): request=10 time=0.4 ms
    
    --- / (ext4 /dev/disk/by-label/DOROOT) ioping statistics ---
    10 requests completed in 9005.2 ms, 2735 iops, 10.7 mb/s
    min/avg/max/mdev = 0.3/0.4/0.4/0.0 ms

    So it's bit of a hit-and-miss.

  • What's the point? Sure i bench a VPS before using it the first time to compare. But i made the experience that even DO has slower IOpings than my other VPS but an apt-get update is much faster in the updating database part.

  • @webflier said: All my nodes with DO get ~200MB/s. (US region)

    I've always received a reply in under 10 minutes.

    I/O in NL is over 300MB/s

  • @KernelSanders said: 3) They're considerably larger than any LEB provider here

    Nope.

  • I don`t get it why people get so bad IO speeds..

    1073741824 bytes (1.1 GB) copied, 2.59217 seconds, 414 MB/s
    @AMS1

    1073741824 bytes (1.1 GB) copied, 2.19469 seconds, 489 MB/s
    @NY1

  • @Makkesk8 said: I don`t get it why people get so bad IO speeds..

    I dont get why people cares about IO speed either. Even 100MB/s is enough. Measure IOPS instead.

  • @ksec said: I dont get why people cares about IO speed either. Even 100MB/s is enough. Measure IOPS instead.

    Quick IO speed = less cpu usage over time = no chance getting suspended or what so ever.

    Thats atleast my take on it ;P

  • @ksec said: Even 100MB/s is enough.

    35 MB/s is terrible though.

  • I really like DO myself. Disk I/O speed isn't a big deal for me, and I love being able to spin up a VPS for next to nothing per hour. I actually use them pretty much as a temp VPS provider; I've never had a VPS with them running for a whole month. And with the free credits, I haven't even paid them anything yet. As for support response times, I've only opened one ticket, but they answered in less than one hour (fifty-four minutes to be exact), which was plenty fast enough for me considering how important the ticket was. Like I said, they make a great temp testbed for a few days, and it costs pennies.

  • TommehMTommehM Member
    edited February 2013

    1GB DigitalOcean server in Amsterdam running ArchLinux
    [root@sql01 ~]# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
    16384+0 records in
    16384+0 records out
    1073741824 bytes (1.1 GB) copied, 6.52793 s, 164 MB/s
    [root@sql01 ~]#

  • heiskaheiska Member
    edited February 2013

    DO down?

    The page you are looking for is temporarily unavailable.
    Please try again later.

    Edit: My VPS is still up, they appear to be doing some maintenance on their website

    DigitalOcean is currently under maintenance and will be back in 30 minutes.
Sign In or Register to comment.