So one huge advantage of having an Atom based netbook (BenQ Joybook Lite U101) has been having a FreeBSD testbed to play around with various technologies before trying to deploy them here.
Currently www.the-eleven.com runs on the venerable Apache webserver using the venerable prefork mpm. It also is using mod_php. Nobody is going to accuse this combination of being svelte, but it is dependable and RAM is cheap these days.
So I've been looking at nginx and spawn-fcgi (from the lighttpd project). With apache the rewrites for web software can be placed in htaccess files and run from there. With nginx, all of the rewrites have to be placed in the configuration files. This can get to be a pain quickly if you have webapps in sub-folders for other web apps.
So as a quick and dirty compromise I've been testing Apache using the worker mpm with mod_fastcgi and php built for fastcgi. Initial tests with apache bench seem to suggest I can get similar performance to the existing setup while using far fewer resources.
So you may notice some flakiness in the site over the next few days as I play with doing a full switchover to this newer model and seeing if it stands up under real world battering by spambots.
And from there I can explore the nginx configuration issues and test to see if that increases output with even fewer resources.
UPDATE: 11:11pm
So I've replaced mod_php with mod_fastcgi, but still running apache with the pre-fork model. I've already noticed a few apps failing with the current config. Hopefully I can update some of those, but they aren't mission critical, so they can wait until tomorrow. If you bump in to problems, like cgi failures, let me know in comments.
UPDATE 1:35p 24 June 2009
So I've done the cutover to the worker mpm for apache httpd instead of the prefork mpm and the change in the apache bench marks are amazing. And the server is using fewer resources.