Hacker News Reader

Comment by malux85 | Hacker News Reader

DigitalOcean is killing it against Linode - I just migrated my last services off Linode because you still cannot attach arbitrary sized disks to your instances, something they've been promising as arriving "soon" for months. Go DO!

View on HN

They both have their pros and cons. Linode offers more RAM for the same price. Linode's load balancers also support IPv6, DO's did not the last time I looked. And Google's Cloud Load Balancer beats both Linode and DigitalOcean hands down in terms of TLS handshakes per second.

Agreed, same exact situation here. Not having block storage in 2017 is nuts. I'm also about to finally move my last server over to DO.

As long as Linode's portal is written in CodeFusion I wouldn't trust it.

They are rewriting it, and it's underlying api.

https://github.com/linode/manager

https://developers.linode.com/v4/introduction

Am I the only one who has constant issues with VMs in Linode? I feel like that platform is the worst out of all the ones I've tried so far. Unfortunately, our company is stuck with it for now. :(

I use the San Jose facility for my Linodes. I haven't had a problem since the rolling power outages years ago where Hurricane Electric's backup power failed to kick in.

Issues like what? I used to have my machines freak out and crash once in a while before moving it all to KVM. Haven't had trouble since.

It's mostly "Hardware issue" errors. We'll get an email from them with the name of the VM saying that an error was detected, and that the issue will be resolved soon. It is generally fixed pretty quickly. It has the side effect of forcing me to learn how to recover from these events, but it's not so fun when my master database's server goes out (that's happened twice in the two years I've been at my current employer). We also have everything moved over to KVM already.

We occasionally experience problems with %steal due to other VMs in the same host. It was a lot worse when we had a critical service hosted in Linode, but that was gutted and moved to actual hardware. Only a small, low-traffic bit still remains in Linode.

Disclaimer: I work there.

What kind of issues are you running into? There's a lot of issues that can happen on a server, but a lot of them are due to not enough resources or a misconfiguration.

Now, if your server is seeing constant issues on the host your server is on...

The emails we get are generally ones saying it was an issue affecting the physical hardware that the VM is hosted on, yeah. :( I tend to just ignore them now though, lol. There are only a few VMs there that are absolutely critical. Everything else is configured for HA.

That's no good, I'd like to take a look and see what's happened - having multiple hardware issues isn't necessarily normal. If you have time, please shoot a ticket our way. Mention that you spoke to Soh on Ycombinator and that I requested this ticket to be opened so we can seek out any solutions.

Reply on news.ycombinator.com