A while back, I migrated my blog from a shared Web host environment to a virtual dedicated server at GoDaddy. Now, before I gripe a bit about the performance, let me say one thing. What I bought from GoDaddy is exactly what I got. It guarantees something like 384MB of RAM for its Windows VDSs, and my blog plus mail server regularly exceeds that amount.

What that means is that when the host that houses my virtual server is under heavy load from the various virtual machines it’s managing, the available RAM allocated to my virtual machine could drop as low as the guarantied 384MB level. Needless to say, if that happens and my apps need more, things might crash. Especially those apps that are already running in RAM at the time the allocation changes.

And that’s what has been happening on my server. Plus, I have discovered it’s getting quite expensive.

As I mentioned in my last entry, my blog typically pulls in around $80 a day or so from ad clicks. Well, this afternoon I had a few minutes to breathe at work and I discovered my server had been offline most of the day. My ad revenue for today is less than $30 as a result. Do that a few times a month and it adds up pretty quickly.

So, I’ve decided that I will once again be moving, this time to a physical dedicated server on its own hardware – an Intel Core 2 Duo running at 2.13 GHz, with 2GB RAM, dual 120GB drive in a RAID array, a Cisco PIX 501 firewall and the works. The reliability and uptime of dedicated hardware is easily justified by saving all the lost revenue from the current system, so it just makes good sense to do this. It’s true what they say: You get what you pay for.

At any rate, the downtime during the transition will probably be far less than the downtime each time the current server fails. Maybe I should install this copy of Exchange I have lying around here and really get things humming. Hmm…

[tags]AdSense, GoDaddy, blog host, virtual dedicated server, downtime, Exchange[/tags]