Totally unrelated to the article, but I've got to put my good word in for Linode. I've never had such good service from a hosting provider, and frankly for a (currently) tiny account.
I use Linode for my primary site and prgmr as the backup. Both are excellent. Prgmr is not for newbies, you submit a public key with your order and get back a login to a XEN console. My hosts there seem to be fine, no problems yet.
This is not accurate. There are many VPS's which are cheaper, many of which have much greater capacity for the money. Some are fly-by-night scams. Others have several years of stability with good support. Check forums and VPS review sites to find the best match.
That said, I have nothing against prgmr or linode and would use them if I needed a super-reliable VPS. (My main VPS is Linode, my secondary is with Kerplunc Hosting)
That's simply false. RAM is the constraint of interest for plenty of single-server websites that are running MySQL as a backend. You want a bunch of memory for the database, plus enough left over to accommodate your web app. That often means wanting a 2-4 GB machine.
Linode is something like $55/GB RAM per month, while prgmr.com is $14.
I remember a post on here saying how hackernews was running on a new 8GB server or something. There's no reason it couldn't run on a 200MB server easily.
(Related: Is HN really sluggish for everyone else as well? Like 3-4 seconds per page load)
haven't had it for long enough , but the bandwidth seems spotty (sometimes 500k, sometimes 2mbit, etc) and seemingly high ssh latency, maybe cpu load on my slice. but other'n that good so far
I used to run a create-your-own-quiz django powered site with 6k uniques/day(in the last few days), with no cache, and it barely touched my 360 vps. You can see some nice graphs here: http://slig.imgur.com/linode
From my experience looking at those graphs, I see that the iorate is pretty low and that the cpu is almost idle. Checking "top", I see that the RAM was sufficient, as there were almost no swap use.
I also use chartbeat.com to see how the users are interacting with the site in realtime. They provide also two useful metrics: user load time and server load time. Looking at those, I can see that the user experience is pretty good, and that the server is up and responding very quickly.
I run a Django-powered site on a 96meg host on an over-loaded Xen host built with ancient P4 Xeon servers (No VT instructions). I use nginx and sqlite to cope with my tiny amount of available memory. With that said the site sees little traffic (<500 hits a day, peaks ~60 hits in 1 hour), but I've never run into issues.
you could go crazy and use a uClibc buildroot. build it on your desktop and transfer an image to your slice. i use slack, but that's not exactly tiny...
I've been running http://wasitup.com on Linode the last months and I've been pleased with their stablity except for a 9 minute network outage earlier today (to their credit they were able to resolve it quickly while communicating the status to us end users). For my opinion on the performance characteristics you'd have to read my article on the matter: http://journal.uggedal.com/vps-performance-comparison
You can blame the ever so unreliable ISP Nac Net, we use them in our office which cut out as well.
"
Good Afternoon,
At approx 12:10pm, we lost communications with some of our equipment in our Newark, NJ location. Upon investigation, it was discovered that equipment located in the cross connect area had lost power. Customers may have noticed degraded internet service for about 2-5 minutes while routers propagated through alternative providers. As of 12:23pm, power has been restored in the Newark, NJ site. We are still investigating the cause of the problem."
Thanks for the clarification. I've been thinking of running http://wasitup.com from 3 different Linode data centers for a while to remedy problems like this (the service currently runs on 3 different racks in the NJ data center). I would first have to find a way to send Tokyo Tyrant data encrypted/authenticated over WAN first.
An easy (if slow) way to do so is to tunnel it through ssh. If things are too slow you can use the "blowfish" algorithm for encryption through the "-c blowfish" option.
Totally unrelated, but I'm very happy with wasitup. Had forgotten completely I subscribed when I got a bunch of emails about a sick server. Really helps.
On the downside I found a couple of emails in yahoo's bulk folder.
If you go by monthly cost per GB of memory or especially storage, Linode is one of the most expensive options out there (~$60/GB RAM, $1.25/GB storage).
The outage was upstream. The downtime was due to the Internet correcting itself by routing around the problem -- if you have access to BGP data, you can see the rash of rerouting that fixed the problem.