This is a read-only archive!

Moved to Linode

My web host for a good long while was Futurehosting. My OS was Debian 4.0 (Etch). Strike one: as of now there's still no option to upgrade to a newer version of Debian. Debian lags so much to begin with, it's really painful ify ou want to use anything released in the past two years.

I had an unmanaged VPS. I ran a bunch of funky non-standard stuff on there and it ran mostly OK. I had to upgrade to get more RAM just so SBCL would run on it, which sucked but I don't know that another host would've been any better.

The good thing about Futurehosting was that they responded very fast to tickets. The bad thing was the fact that I had ample opportunity to know this. The server would go down randomly once every month or two. I'd open a ticket saying "Hi my server is down", then things would be working again in a half hour, but why did this happen so often? I don't know. An awful lot of "failed switches". I wonder how often this happened without my knowing about it, given how often it happened in the middle of my using the server for something.

With all the hardware they were burning through I would've expected upgrades or price reductions over time, given that I was a steady customer for so long and that disk space and memory keeps becoming cheaper and cheaper in the world. But the prices always stayed the same, which was another strike.

Being hosted there was annoying but never annoying enough to switch. And migrating all of my sites and data to another server seemed like a huge pain. Momentum: the worst enemy of progress.

I moved to a new host on a whim recently: Linode. It was far less painful than I expected. Thanks to Linux and plaintext config files, it was mostly a SCP-it-all-over and tweak process. It took me one evening and a bit of time the next morning. Linode offers a lot of OSes which is also nice.

I pay less for Linode than I did at FH (and I get fewer resources at Linode, but I don't need much). Thus far I'm astonished how much faster things are running on the server. Even goofing off at a terminal, the shell is more responsive. My email loads instantly in kmail instead of lagging for a second. I never knew what I was missing. Linode's DNS control panel is also pretty braindead simple to use.

Futurehosting gets a C+ from me. It worked and my website existed, but it didn't knock my socks off. Hopefully Linode is better.

August 15, 2009 @ 4:03 PM PDT
Cateogory: Programming


Quoth Bleys on August 15, 2009 @ 7:50 PM PDT

FH doesn't get a C++ from you?

dodges rotten fruit

Quoth Gen2ly on August 16, 2009 @ 1:11 AM PDT

Momentum: the worst enemy of progress.

Nicely said. Been looking for a hosting service, thanks for the tip.

Alex Paes
Quoth Alex Paes on August 17, 2009 @ 2:34 AM PDT

I've been using Linode myself for a little over six months and i'm really happy with it so far. Before going with linode i used slicehost but didn't like their support so i decided to move after 2 months and i'm glad i did it.

Quoth Brian on August 17, 2009 @ 5:11 PM PDT

Good to hear. I almost went with Slicehost but went with Linode at the last minute when I read they'd been bought by another company.

Quoth circuit_breaker on August 19, 2009 @ 11:31 PM PDT

I've had a Linode for years

Been very very happy

The people that run it make them selves very accessible via IRC as well (caker is friendly too)

Couldn't recommend them more.

Quoth Curtis on August 31, 2009 @ 9:35 AM PDT

If you don't mind a n00b kind of question, do you run multiple domains with Hunchentoot (virtual domains?) and, if so, how do you do that?

Quoth Brian on September 02, 2009 @ 5:13 AM PDT

You can use Apache2 with mod_proxy and forward requests to Hunchentoot. Set up virtual domains in Apache and have your Hunchentoot instances listening on different ports on localhost and forward requests to the proper instances.

I don't use Hunchentoot since I switched to Clojure but it works the same for both.

Quoth Enigmatic on October 09, 2009 @ 8:28 AM PDT

Which package did you buy? I just got in trouble for running over my memory limit when setting up a new compojure app on another host. Do you use apache to front-end your compojure apps? Any memory tips? Thanks!

Quoth Brian on October 17, 2009 @ 5:28 AM PDT

@Enigmatic I have the "Linode 540" plan and it's good enough for my needs. I use -server -Xms32M -Xmx128M flags to the JVM, for what it's worth.