Xserve Notes

Moving to a Mini Server

September 25, 2005:

I recently got a new Mac Mini (1.42GHz, 1GB RAM, 80GB disk) which I hope to use as a small, quiet, but very capable replacement for my aging blue and white PowerMac G3 (350Mhz, 256MB RAM, 4GB disk) which is running Mac OS X 10.3.4 Panther Server. This trusty Web server has been used by my family and also serves several other Web sites of mine with various boutique domains.

It has run pretty flawlessly for the past couple of years, during which time I’ve also added a couple of blogs, Movable Type and, more recently, PixelPost. I used to run a mail server, but it succumbed to massive waves of spam a couple of years ago and I since moved all of my mail accounts to Digital Forest (http://www.digitalforest.net) which enables me to leverage the excellent spam service (Postini) to which they subscribe. Well worth the money as this has been very reliable and my family no longer hounds me about email problems. On the rare occasion when Digital Forest goes down, maybe 2 or 3 times a year, it’s usually back on line pretty quickly and everyone is happy. If not, at least I can foist the blame off on them.

The blue and white PowerMac, which came out in 1999, was the first Power Mac that came in the cool new plastic case with built-in handles, taking a cue from the fabulous colored iMacs of the day. More about that model can be found on this Apple history page. 6 years later, the Mac mini is least 5 times the speed, with 4 times the memory and 20 times the disk space. My mini also has bluetooth, WiFi and the ability to burn CDs & DVDs all in a package that's about a tenth the size and probably about half of the original cost of the blue & white G3 in 1999. The wonders of computing in the 21st century!

My plan was as follows:
1. Set up Mini with Tiger Server
2. Migrate Web data, accounts, MySQL data
3. Configure various files for Movable Type and PixelPost
4. Get it all working
5. Switch the servers (get my router to point to the new server for all Web services)

I did a clean install of Mac OS X 10.4 Tiger Server, upgraded it to the current 10.4.2 release and all was fine. But I suspected that the real fun was just about to begin!

VNC on OS X Server

I use VNC (Virtual Network Computing), a cross-platform, open source protocol for allowing remote control between different types of computer, to remotely administer the GUI on a number of different servers. Thus one of the first things that I wanted to get working after my initial install of OS X Server was some form of VNC so that I could install the server in my rack in the basement, but still run it from upstairs.

Apple does support VNC , in both OS X 10.4 (Panther) Client as well as OS X 10.4 Server. To turn it on, go to "System Preferences" and in the "Sharing" panel click on "Apple Remote Desktop". Then click on the "Access Privileges" button and turn on "VNC viewers may control screen with password" and enter a password. When you click "OK" you can then click on the check box next to "Apple Remote Desktop" to turn on the service.

Now you can connect to the OS X  GUI via any VNC client and the password. I like free Chicken of the VNC on the Mac, and Ultra VNC Viewer on the PC, but some people swear by RealVNC which has versions for many platforms.

My personal experience with the default VNC server in OS X is that it is a little flaky, probably because the service appears to be oriented toward allowing the Apple Remote Desktop administrative server software to update client computers, rather then focused on the VNC functionality.

Thus I instead use OSXvnc, an free VNC server. You need to make sure that Apple Remote Desktop is turned off in the Sharing panel, but once installed in your applications or utilities folder it appears to offer a much more reliable VNC experience.

One particular thing that is interesting about the most recent version of OSXvnc is that now it offers a capability to have different people using multiple desktops at the same time -- normally VNC only gives you access to the primary monitor that must be shared by all ciients. But taking advantage of the Fast User Switching capability of OS X, now each user can use a different virtual desktop.

Another useful trick that you can do with  VNC is to allow multiple machines with monitors that are side-by-side use the same mouse and keyboard, even if they are not on the same platform. If you have multiple monitors, this eliminates the requirement of KVM switch.  I've not used any these tools yet, but osx2x looks very Macintosh centric.

There are some other good links at the excellent Tao of Mac blog under the VNC tag.

OS X First User

A note for "Best Practices":

During a fresh install, the OS X installer will ask for the name of the first user and will give this user a different set of default items in the Dock. As you typically will be making a disk image of this install for future recover, use "Administrator|admin" and a long-term memorable group root password for this first user, rather then your own name and private secure password, as it may not be yourself that reinstalls the server.

Mysteries in Anandtech's "No More Mysteries"

Anandtech published this summer two articles very critical of OS X Server's performance as compared to Linux:

• No more mysteries: Apple's G5 versus x86, Mac OS X versus Linux

  The server performance of the Apple platform is, however, catastrophic. When we asked Apple for a reaction, they told us that some database vendors, Sybase and Oracle, have found a way around the threading problems. We'll try Sybase later, but frankly, we are very sceptical. The whole "multi-threaded Mach microkernel trapped inside a monolithic FreeBSD cocoon with several threading wrappers and coarse-grained threading access to the kernel", with a "backwards compatibility" millstone around its neck sounds like a bad fusion recipe for performance.

  Workstation apps will hardly mind, but the performance of server applications depends greatly on the threading, signalling and locking engine. I am no operating system expert, but with the data that we have today, I think that a PowerPC optimised Linux such as Yellow Dog is a better idea for the Xserve than Mac OS X server.

• No More Apple Mysteries, Part Two

  It is clear that if you plan to run MySQL on Apple hardware, it is better to install YDL Linux than to use OS X. If you need excellent read performance, the maximum performance of your server will be up to 8 times better. If your server is only going to serve a limited number of users, YDL Linux will allow you to run with a less expensive system.

  If the usage pattern of your server is more OLTP, Transaction processing oriented, we give you the same advice. Our quick tests with InnoDB show the same kind of behavior and we have noticed very slow file system performance. At this point, we do not have enough data to be conclusive. We noticed, for example, that importing data in our database (via the ">" command) took up to 8 times longer.

Apple lost a sale last summer to one of my clients due to a lack of response on these articles. My Apple Xserve representative said that they were aware of the articles, but was told to say that there was no official response.

I still find the results quite mysterious -- is it only mySQL? Is it thread creation? What about Postgres which I don't believe uses threads.