Linode NextGen: RAM Upgrade
blog.linode.com
blog.linode.com
Digital Ocean has become quite a competitor (and I have a box with them now for a staging environment) but the fact that they do not provide a private/internal network between your boxes is something that I can't live without. I like to keep app servers and db servers isolated from the real world by one box in front of all of them ... which is not something you can currently do with Digital Ocean.
I love Heroku's platform and think they've done some amazing things for our industry, but I don't agree with any of their recent PR moves. Linode, on the other hand, has never stirred up drama or bullshit since I have started working with them. They're straight shooters and this gives me a great deal of confidence.
I had a personally hair raising experience this weekend trying to migrate a smaller server that kept swapping over to a larger one without too much downtime. I was able to do this pretty painlessly but man I wish I would have waited just a few days for this!
Digital Oceans lack of "private" network is silly, if you really need it, setup a encrypted tunnel yourself, I would not trust anything else anyway. Also I highly doubt that if your DO DB and App server talk the traffic leaves the datacenter, but you could test this.
On the other hand as far as I know DO don't tell how many VMs share a host.
Here is a counter example, imagine I have two VM host servers with 16 logical cores. On one I could pin each VM to 1 logical core, on the other I could run 300 VMs and give each VM 24 logical cores... The first one is going to perform much better.
Also some hypervisors (for example VMware) only executes a VM when they have as many cores as the VM has cores available for execution. So having many logical cores in your VM can negatively influence CPU scheduling.
"And support is a joke." Not in my experience
You don't know if the first one will perform better or not. It depends on the workload of each VM. If most of the VMs are idle most of the time, when one of them needs CPU the second setup may even perform better.
And I doubt that Linode runs more VMs per host than DO. Judging by the pricing is probably the other way around.
Based on the benchmarks I've seen, it appears that Linode really does give the kind of concurrency you'd expect from four cores (i.e. if your problem is parallelizable, you can scale up on Linode better than Digital Ocean, whereas Digital Ocean will work much better if your program is serial and needs to hit the disk a lot).
Good thing Linode and DigitalOcean don't use VMware.
Your hand-waving about the hypervisor is unwarranted, since hypervisor interference under Xen shows up as its own time from the perspective of the domU (steal%) and nobody worth mentioning actually does hosting with VMware.
How long ago was this?
By all means, encrypt your traffic on the private network if you're so inclined, but encrypting across the public IP space and encrypting across RFC 1918 space do not accomplish the same goal, particularly not with the same latency or redundancy characteristics.
Nothing about the use of a public addresses forces an extra hop in the way you suggest.
$20/month is prohibitively expensive for one-off side project hosting and there's lots of utility to be had from a cheap low-RAM, low-CPU server. I'd buy 10!
(Note that I'm not intending this to refer to you specifically, since you're already a subscriber anyway.)
Thus when you segment the market by "people who can afford $20-100/month", you are also segmenting the market by the correlating variables "people who are mad at their current host" and "people who can spare several days to migrate their infrastructure".
As a member of that class who migrated to Linode, I can attest that the size of that market is nonzero. But I can also attest that a great many projects start and remain on AWS and lowendbox where the barrier to entry is much lower, and even as a satisfied Linode customer I continue to start and continue to maintain many projects in those environments.
The hourly, broken-up billing is a smokescreen; for exactly what you get out of a (now) Linode 1024, you'd pay $50+/month or so on AWS. Don't forget total bandwidth, an elastic IP, and so on.
The ongoing TCO of AWS is much higher than Linode, of course. But that's precisely my point: you want to capture customers at birth, incubate them into adulthood, and then charge them a lot of money now that they can afford it.
Although if you want to be pedantic, let's say "actually useful, potentially-production barrier to entry". There. Fixed.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts_...
I don't find my cheap t1.micro based IRC bouncer / VPN / reverse SSH endpoint / static-content generation box to be an awful joke at all. They're quite useful for many things.
There are $10 VPS solutions out there, but their poor reputations lends credence to the idea that $10 VPS solutions are not where the money is at.
Its not a smokescreen if you are using AWS for a cloud (e.g., dynamically provisioned according to need) server infrastructure rather than as a simple VPS.
One of the biggest costs of running a SaaS business is support. I'd guess that there's not a whole lot of difference for Linode in the cost of supporting a $10/month vs. $320/month box. In fact, there may be negative correlation -- I wouldn't be surprised if the cheaper customers are more expensive.
Now, your argument hinges on there being a high conversion rate from low-end plans to high-end plans. I'd guess that rate is quite low, in fact. Most accounts probably never upgrade and / or cancel after a few months. Now, the canceling in the first few months is a big problem as well, because for most SaaS businesses, your biggest support cost is going to be concentrated in those first months where the customer is getting set up. I wouldn't be surprised if it takes Linode a few months, on average (not median since support isn't evenly distributed), to get into the black on the low-end accounts.
The variables in that equation are really important in deciding if it's worth putting up with cheap, less knowledgable, high churn customers just in the hopes of upselling them over time, or if it's better to slice off the segment from the beginning that finds $20/month to be onerous.
Being unprofitable and not being able to spend $240 / year is a different issue.
The first is about the project being unprofitable. The second is about you being broke or not believing on it to spend even 1/150 of your income (I'm speaking of course for US/EU citizens/wages).
There are however other vendors that have even $5/month plans for VPS (and even offer SSD drives). Try Digital Ocean.
Alternatively, Hetzner will give you a 512MB VM for about $10.34/month.
SNI: http://www.digicert.com/ssl-support/apache-multiple-ssl-cert...
Normally this isn't a problem, except that some browsers nowadays default to requesting the HTTPS version first. That means if you're serving an HTTP site and an unrelated HTTPS site, and a user accesses the HTTP site via an HTTPS connection, there's a good chance you'll end up serving the unrelated HTTPS site plus an SSL warning instead, because that's how Apache does things.
How is that Apache HTTPD's problem? Nginx would do the same thing. When you don't define a ssl version of site.com for ip:443, you get whatever the default cert/vhost is for that ip:443. What would you have a webserver do differently?
Sure there are other options but I'd rather not have accounts all over the place, and I like Linode.
Linode's problem with $10 accounts is not with customers like you who are paying them decent money otherwise - it's with customers who would sign up for $10, break things and expect $50 a month worth of support on an ongoing basis.
Most customers looking for a cheap VPS (to learn on, to experiment etc) are not going to be profitable unless you provide virtually no support, so by slicing off that part of the market they can offer a uniform level of service without compromising their profitability.
How about not revert to a "default"? Just serve a redirect to the HTTP version if a HTTPS is not available for that vhost.
1st site: https://www.firstsite.com:12345/
2nd site: https://www.secondsite.com:24328/
3nd site: https://www.thirdsite.com:37712/
etc.
You can have thousands of HTTPS websites on a single IP address while fully supporting every browser.Prgmr is also really great too, 64MB for $5/month (by comparison, 512MB for $12/month). Run by an HN fellow, so that's also a plus.
EDIT: goodness gracious, i didn't realize that literally everyone in this thread is mentioning DO when I wrote this post!
It's not the same as $10 a month but it's less than $20 and their support is excellent (5+ year customer, but more for their excellent DNS management console.)
/e Apparently google sent me to the dutch one by default! Thanks google!
Your package is only € 5/month now - for €10 you get 4GB/150GB/5TB which is only the quarter of the price of an almost equal (no SSD, but more HD and traffic) DO instance.
https://www.transip.eu/vps/pricing-and-purchase/
Almost unbelievable.
Still a great deal though :)
Personally I've started using Digital Ocean for those smaller non-production servers (staging, dev etc). I still wouldn't trust DO for anything production.
The Linode service and support is second to none, and I'm happy paying the price (which now gives effectively twice the value!).
The interesting thing is that linode started out as a cheaper alternative to slicehost, so its ironic that they are now trying to differentiate themselves in much the same way slicehost did back then.
Linode have been around since 2003. I think Slicehost was founded later than this (in 2006 according to a quick search for their name.)
This is correct. I signed up with Linode in 2005 and there was no Slicehost then. I was moving from another VPS provider (Redwood Virtual) which had twice the resources for the same price as Linode but were really, really crummy (they don't even exist anymore). That experience really taught me the value of considering quality in addition to the price/feature ratio, which is why I'm not jumping ship to DigitalOcean. (I might if/when they establish a solid reputation, but no sooner.)
You have that backwards, given that Linode predated Slicehost by upwards of three years.
- Provisioning is conceptually cheap, and this is their killer feature. You click the "Make a new VPS" button, you pick your distro, how much RAM you want, and an SSH key, and they spit out an IP address less than a minute later. `ssh root@198.xxx.xxx.xxx`
This is much nicer than eg. finding or downloading a box to mess with Vagrant or taking who knows how many hours to set up your own distribution in VirtualBox. Just a few minutes ago, I spun up a box, messed around with Gitlab, and destroyed it. Completely seamless; has all but replaced VBox for these "one-off VM experiments" that I sometimes try.
There's also an API for automatic provisioning if that's your thing.
- Pricing: Cheap, as you'd expect. 512MB for 0.7¢/hr or $5 a month. There's no difference between monthly and hourly pricing so if you want to pay a buck fifty to rent the 24-core 96GB monster for an hour, have at it.
The thing about DigitalOcean is that they're still such a new service that they haven't gotten everything all polished yet:
- No kernel upgrades. The kernel is kept outside of your virtual machine, which means that if you upgrade your kernel, then you'll get mismatched modules and your network interface won't come back. They've pinned kernel updates in ubuntu so this shouldn't be a problem, but you have to say "IgnorePkg = linux" in your /etc/pacman.conf if you're on arch. Security updates will be a pain though...
- You can't boot into a recovery image/liveCD. If the above happens to you, I assume you'll have to either restore from backup or file a ticket and ask them to pick things out of your VM's hard drive. (You do get raw console access provided by an HTML5 VNC client, which can be useful)
- Payments are weird because you can't see your VM or network usage, so it's unclear how much you'll be charged until they bill you at the beginning of your month. If you select to pay via paypal, you can't pay by a credit card linked to your paypal account (at least for the first transaction any way); I had to give them my credit card information directly. (I imagine they do this to cut down on fraud or spam)
- Services are still a bit barebones. You have to roll your own load balancing. There's no support for mounting an image into another VM to recover files. No internal networks; every VM has a public IP address, which makes me curious to see how they're going to handle IP address depletion if they ever get popular. You have to use your own firewall via iptables or similar.
They will manage your DNS for you though, if you like, and you can ask them to take a snapshot and automatically back up your VM every day or so.
My verdict? I think they're lovely and I really reccomend them especially for personal projects, but as of this writing (early april 2013), you should think about these things before you decide to use them in production.
> There's also an API for automatic provisioning if that's your thing.
Oh, it is, and I wish these comparisons would consider the API more, since deploying a node via Linode's API and DigitalOcean's API are probably comparable. Declaring "my UI is faster!" as a sales point is disingenuous, since Linode is merely offering more choices during the provisioning workflow. Since you're saying "click", I assume you mean the UI too; at scale, absolutely nobody uses the UI any more. I manage a fleet in the thousands on AWS, and the last time I logged in to the AWS Web Console was about six months ago. It takes at least two minutes of clicking to spawn an instance in Amazon, but earlier today I launched 38 instances in about thirty seconds using the API.
> - No kernel upgrades. The kernel is kept outside of your virtual machine, which means that if you upgrade your kernel, then you'll get mismatched modules and your network interface won't come back. They've pinned kernel updates in ubuntu so this shouldn't be a problem, but you have to say "IgnorePkg = linux" in your /etc/pacman.conf if you're on arch. Security updates will be a pain though...
This isn't unique to DigitalOcean and is fundamental to the way Xen works (the kernel is loaded by the host, not the domU). However, Linode solved this problem better by providing kernels with most modules that you'd ever need built-in. You can upgrade all you want on your filesystem and not run the risk of hosing your machine, because your modules generally aren't considered at all. You can still add them by compiling against the upstream Linux sources, but the core modules aren't loaded from your filesystem (on my Linodes, my modules/ directory for the running kernel is empty). There's also a loader for your own kernel on the filesystem, PV-Grub, which DigitalOcean doesn't do.
> - You can't boot into a recovery image/liveCD. If the above happens to you, I assume you'll have to either restore from backup or file a ticket and ask them to pick things out of your VM's hard drive. (You do get raw console access provided by an HTML5 VNC client, which can be useful)
Only if you screwed networking. Lack of recovery = showstopper.
Here's the docs for DO's API: https://www.digitalocean.com/api I agree that UI isn't strictly necessary, but the reason why I brought up the UI was because as an "amateur" user, that's what I care about.
Digital Ocean uses KVM, not Xen, per https://www.digitalocean.com/faq so I'm not sure why they would need to pin the kernel.
Why are you doing that?
And since you mentioned it, I have been following their Twitter replies and apparently private networks are coming soon (https://twitter.com/digitalocean/status/321650732703023105).
This is much nicer than eg. finding or downloading a box to mess with Vagrant or taking who knows how many hours to set up your own distribution in VirtualBox."""
I don't get this; finding or creating a base box for each disribution you want to use is a one-time cost. There are many existing boxes listed at http://www.vagrantbox.es/.
Checkout www.lowendtalk.com/.
BuyVM.net is also very reliable and competitive for what you get.
http://www.doesbuyvmhavestock.com/
They actually have stock which only seems to happen a few times a year.
http://quickweb.co.nz/lowendbox.html
I've been using these guys for small projects for about a year now - never a problem.
$7.30 / month for a 0.25G instance (on the members plan)
$11.68 / month for a 0.5G
$22.63 / month for a 1G
I've worked with them a lot, and they are excellent. The underlying hardware is really, really fast, their tech support guys are very competent, and they are highly responsive.
If you're capable of using a bare-bones Linux VPS but are unable to pay $20/mo for your side projects, it's time for you to find a better paying job.
Bottom line: it has nothing to do with income, but what people value.
Looks like their (Digital Ocean's) pricing shook linode's cages a little bit, and that's a good thing.
The one aspect that has me considering going back: Linode's backups seem much more confidence-inspiring.
On the other hand multiple CPUs only matter if you have a ton of traffic. My side projects do not :) At least for hobbyists Digital Ocean is very compelling.
Also in the case where you're running with swap because you don't have enough memory, SSD comes in handy too, mysql is particularly badly behaved in this respect, it swaps too easily unless you load the entire db into memory by setting innodb_buffer_pool_size equal to the size of the db + a little bit.
long story short, an SSD can help out quite a bit more than you seem to suggest.
There are definitely some things where disk IO is important, but swapping should not be in that equation unless you have a problem. I prefer better CPUs and Memory to disk IO on servers usually. The database server is the only server I care about having decent IO, and Linode does have decent IO for non-ssd drives (a lot better than AWS).
Why do you say Linode's backups are more confidence inspiring though?
Partly it's observations over the past week. I noticed a few days after moving that I had two backups the day I created my account, and no backups for 3 days after. Contacted support and was told they have some 'randomization for load balancing'. Asked what the worst-case frequency could be, and was told it's "usually 24 hours". This is the kind of thing that can bite you when the shit hits the fan.
(And the experience definitely shows what other commenters said about Linode's support.)
Do you work for digital ocean? how did you get this info?
After waiting some weeks for Arch to be re-released I finally booted an Arch image. Not a week had passed and some kernel upgrade had already made the system unavailable (no network on vm). I forced nothing, just ran sudo pacman -Syu as I always did on Linode.
Support didn't care. For days I tried responding to the ticket that I opened, talking to them on the irc, via mail. Nothing. I tried to request help to at least recover the files. Nope, nothing they can do.
I did not understand the true value of good support. Now I do. Back to Linode.
The fact that he didn't get any help is a problem that is what support is supposed to do and if he expects a higher level of support than Digital Ocean provides and Linode provides that I see no problem.
(The use case in this thread is backups as voidlogic mentioned.)
And yes linode has this: http://www.linode.com/wiki/index.php/Finnix_LiveCD_Recovery_...
This was DigitalOcean's fault, for not supporting changed kernels without providing safeguards against kernel updates.
This does play catchup, and the things that they have had in private beta are pretty nice too... but whether it will make a difference is yet to be seen.
Hosting is far more a retention game than pure acquisition, these changes are long overdue... SSDs are also overdue.
Random observation: The Linode 1024 is now the same price as prgmr.com's equivalent.
I'm sure it's a good deal all around, but it seems like a slight of hand to me: Linode, now with more RAM, AND more expansive backups for the same disk space.
--------------- Hello,
The backup prices are shifting just as the RAM prices shifted, so Linode 1GB backups are now $5, Linode 2GB is $10, and so on.
I hope this clears things up. Please let us know if we can be of further assistance.
Regards, Jonathan --------------
Interesting... the Fremont data center had some pretty serious issues a couple years ago, and though it has been better since then the bad memories remain. I wonder if they're finally switching to a different data center vendor.
A while back I spoke to the Linode guys (I think it was at SXSW 2011) and they said they were going to be releasing an EBS-like product "soon". But I guess not that soon.
Perhaps I'm just not a good fit for Linode in this case? Any thoughts?
Disclaimer: They're Dutch and so am I, so you should factor national pride into this endorsement to some degree.
Other than that, there are probably VPS providers who let you upgrade disk space independantly from RAM (I'm using Europe based providers, so I probably can't give you relevant names, unfortunately).
And it has been fantastic when it comes to speed and whatnot.
Update: The traffic is a bit expensive though.
When I looked at their site I didn’t see information about what kind of SSDs they are using and, based on the price, assumed they are MLC (consumer grade). I’d never want that on a server.
I've been working on a HN clone. The HN codebase creates a ton of small files for storage (one per post or comment), which need to be loaded up en masse on startup. Switching to Digital Ocean from Linode reduced startup time by 50x.
We did an interview with Linode last month about some of their new upgrades: http://blog.serverbear.com/interview/linode/
You can also see some benchmark data from the new E5 CPU's here:
Dallas - http://serverbear.com/benchmark/2013/04/07/FxVC0fV6q5GAMa1j Fremont - http://serverbear.com/benchmark/2013/4/6/TX3w1Zx5dRK13MJi
Linode is very painless, but as always, that convenience comes with a cost. I am very sad that they do not allow for extra IPs anymore. I let my service lapse one month and lost my extra IP.
(Don't forget to increase swap sizes, change configurations to deal with extra memory, etc)
I understand why Linode follows that procedure. I just miss the old days. I have to be more careful about cross porting, cross data, cross domains, and hosts which can't access anything but port 80. I used to just follow the principle of website x, y, z on port 80 on IP1, website a, b on port 80 on IP2.
Luckily, digital ocean basically sells ips for $5/pop.
Linode is definitely the strictest in my experience when it comes to enforcing ARIN's rules (if HTTPS is your justification, Linode actually checks to make sure you're serving up a valid certificate). This is a good thing for the Internet but somewhat frustrating when other providers are so much laxer.
Their cloud server management tools are a joke compared to Linodes.
My curiosity got the better of me and would have preferred to have planned a bit better for the downtime but am now 23 out of 28 in a queue and moving pretty fast...
http://workforpizza.com/posts/2013-04-04-comparing-apples-an...
I did notice though after the migration (512->1024 Dallas) I'm now on a node with the older CPUs (model name : Intel(R) Xeon(R) CPU L5630 @ 2.13GHz ) as opposed to the E5-2670s mentioned in the blog March 18th.
* You: Intel(R) Xeon(R) CPU L5630 @ 2.13GHz * Me: Intel(R) Xeon(R) CPU E5-2630L 0 @ 2.00GHz
(cat /proc/cpuinfo)
Interestingly, the largest providers AWS + Rackspace provide no free bandwidth, while Linode not only included it, but increased it significantly. Will these providers push the bigger guys to start offering free bandwidth which is a significant cost of the product [well, if its used].
I'm currently running 2x512mb instances at Rackspace. (It's cheaper than 1x1024 instance, sadly, and I don't need the extra bandwidth/disk space, just the RAM.)
I think I'm going to spin up a trial today. Though I tried to do the same w/ digital ocean and my CC is giving me nothing but headaches. Thanks for the link!
Opened a ticket 6 minutes ago :o
It was highly disappointing. I hope you have a better experience.
~1min in queue and 5min to migrate 512MB to 1024MB.
However I'm still on old CPU. :/ Intel(R) Xeon(R) CPU L5520 @ 2.27GHz 8 cores Memory 1001 MB real
Shall we stop and Concentrate on Linode now please..
Your position is 160 out of 389 queued migrations in this Linode's datacenter.
I got mine to migrate ahead of the queue by accident. I just resized my disk, and it started migrating after the resize.I can't wait to hear their "upcoming explanation", and I hope it's along the lines of "we're nuking it from orbit".
Edit: Ah, just misread the console. It's still "copying" my empty drives, at the advertised rate. So dividing your disks by the 40ish MBps is a good estimate of migration time.
http://blog.linode.com/2013/03/18/linode-nextgen-the-hardwar...
http://blog.linode.com/2013/04/09/linode-nextgen-ram-upgrade...
Are they really going to make all their customers go through two migrations? That would be disappointing.