Live data from Hacker News

The Meteoric Rise of DigitalOcean

news.netcraft.com

41–50 of 164 posts

Re: The Meteoric Rise of DigitalOcean

#41
post #36

I am curious if there are any IOPS comparisons between DigitalOcean and real hardware (spinning disks)? Currently we run our Postgres instances on EC2, but are looking to move to get better IOPS. The question is: SSD-based VMs or real hardware? Cost is also a factor which is why DigitalOcean is a contender.

iops are available on serverbear http://serverbear.com/9806/digitalocean

Re: The Meteoric Rise of DigitalOcean

#42
post #32

Given how cheap the price is, I don't think they have a sustainable business model. As far as I can see, there is nothing technically different from their model that allows their service to benefit from any type of economies (of scale/scope) in order to stay competitive. So then my overall question is - how can they offer better service and better hardware (i.e. more expensive) at a cheaper rate? I'm genuinely curiou…

They offer the same amount of RAM for less than Linode, but they offer fewer cores, which makes me suspect they're putting more VPS's on a single host. I haven't yet run any benchmarks, but I think Linode gives you more CPU and Digital Ocean gives you more memory. It's a little more complicated than "better service and better hardware at a cheaper rate."

Re: The Meteoric Rise of DigitalOcean

#43

I've played with DigitalOcean some. But I've kept my main VPS on Linode, and also recently recommended Linode for a group that I'm peripherally involved with. Using SSDs for multi-tenant virtualized servers seems like a good idea to me. My intuition on this may be wrong, but it seems to me that the lack of variable seek time ought to lessen the variability in I/O performance that one hears so much about. However, I h…

I asked them about IPv6 in January and they said "coming later this year". I'll certainly give them a closer look when that happens.

Re: The Meteoric Rise of DigitalOcean

#44
post #36

I am curious if there are any IOPS comparisons between DigitalOcean and real hardware (spinning disks)? Currently we run our Postgres instances on EC2, but are looking to move to get better IOPS. The question is: SSD-based VMs or real hardware? Cost is also a factor which is why DigitalOcean is a contender.

Depending on the size of your existing DB and the workload getting a larger sized VM - 16+GB you should see significant performance improvement.

Because it's hourly you can spin up and test and if it doesn't suit your needs will be a minimal charge.

We also made a promo code : NEWSYC10 - so you can get a $10 credit to test with before incurring any charges.

Re: The Meteoric Rise of DigitalOcean

#45
post #25

The performance/price is good but the server is not reliable at all. Pingdom tracks many 1-minute downtime during the week. I think they have problems in the network, maybe because of the growth? Their support is very good though, I once got $50 credit because the machine/cluster that hosts my VPS was broken...

I've also had the pingdom monitoring on a droplet for the last 2 months and the only downtime I've been alerted to was my fault. Maybe it's on your end?

Re: The Meteoric Rise of DigitalOcean

#46
post #40
post #37

Earlier quoted context omitted.

This doesn't sound sustainable. Four years from now, DigitalOcean will have a mix of machines just like the other hosting providers. (Google Compute Engine is in the same position because right now they only run on Sandy Bridge.)

DigitalOcean is my fourth host in four years. I just spent two years with a company inexplicably named Reliable Hosting Services before I switched. Switching hosting providers is surprisingly easy, since I just replicate out my DBs and then eventually switch the primaries over to the new host. My gut tells me that DigitalOcean has at least a couple years until I have to even think about comparing to other hosts again…

We're happy to have you on board! =]

Re: The Meteoric Rise of DigitalOcean

#47

Recently tried out DigitalOcean for a couple of small projects and already noticed some network reliability issues. My droplet was un-accessible for a couple of hours (at least) yesterday. Fortunately, it was for a non-production project and they were able to restore it within about a 1/2 hour. Verdict is still out for me, although I suspect that reliability will improve with time. I'm keeping production at Linode.

I noticed the same thing when I initially switched. I actually had them lose the box I was on, and the backups associated with it. They apologized and indicated it was an issue at the datacenter that they didn't have much control over. They gave me a really nice bit of credit on my account and I've since had no problems. I'm a fan of the pricing as well as their support.

I'm amazed you stuck with a host that lost your data. That would be a complete deal breaker for me; I've never lost so much as a byte with Linode over six years.

Re: The Meteoric Rise of DigitalOcean

#48
I've been on DO for several months now and love them. And as far as reliability, I've had binarycanary pointed at my sites for about a month now with one outage that lasted about a minute and then resolved itself. To me, for the price/benefits, that's amazing.

One other thing people rarely mention with hosting, that's SUPER important to me, are the FAQs/Docs, and DO really comes through in that area imo.

Re: The Meteoric Rise of DigitalOcean

#50
post #35
post #13

I moved everything I had at Linode over to DigitalOcean as well and performance has been excellent. I loved Linode's stability but their response to the recent security incident really pissed me off. On DigitalOcean, I have seen briefly the network issues mentioned by others, but things have been more stable the last month or so. That said, one production server I work with on RackSpace was completely unavailable yes…

Have you integrated something like Puppet or Chef into your workflow to ease the pain of spinning up specific servers such as app, db, workers, etc.?

We're actually working on that now.
Post reply on HN