On Thursday, we began making a tough decision – what to do about Xatu. If you’ve been following Sabrienix’s Twitter, which is where we store our status updates, we’ve had a spot of bother with him lately. The uptime stats linked in the previous post look awful because of him and Vaporeon (but Vaporeon’s outage was my fault), and basically the underlying cause is this: FreeBSD 7′s disk performance under XenServer sucks.
No one who currently works for Sabrienix has a good enough knowledge in Linux for us to run it for our web services – we’re pretty much a FreeBSD shop. I have about a decade of experience of administering, programming and troubleshooting FreeBSD so we have a certain amount of confidence in running it – unfortunately Xatu’s datacenter doesn’t support FreeBSD “officially”, so we ran FreeBSD under XenServer.
They brought it to our attention that there was an un-supported method for installing FreeBSD on their machines, so we organized to have a new server set up that I could put FreeBSD natively on… the difference is astounding. On identical hardware, Apache can take over 100x as many hits – not to mention we got rid of the Hypervisor from RAM.
The new server is named Arigeitsu – we decided to not be quite so obvious about naming our servers after Pokemon and go with romanized Romaji names from now on – and if you’re reading this then you’re loading off him instead of Xatu. I’ve moved a couple of my personal sites over for a test to see how things go, and so far I’m pretty impressed.
Right now I’m working on getting Murmur compiled, so we can do away with Wurmple as well as Xatu (though I have a good many sites to migrate from Xatu first). It’s going to be a long weekend, but the results will be worth it in the end.



