The Super Cache pages says “Mod Rewrite is used to serve the static HTML pages. As fancy permalinks is also a requirement it should already be installed”.
Apache is notoriously slow for serving static content, so I wonder if it’s possible to serve those static HTML with an alternative webserver such as LightTPD or Nginx, that would make Super Cache even better.
I know Donncha and the WP sites use LiteSpeed, which I think it’s a big mistake — LiteSpeed is not only a commercial product, but it’s closed source and most likely includes code from LightTPD and / or NGINX which are free. WordPress is already benefitting this commercial venture being the posterboy for LiteSpeed, which has very expensive licensing (they charge $250 PER CORE in your server, a dual opteron 280 would cost you $1,000) and they also delve in censorship with a policy that bans its use for legal adult content (I wonder how come WordPress.com runs LiteSpeed, when it’s chock full of adult content to the point of being banned in Turkey?).
Anyway, I think WordPress should use its considerable clout and influence to foster the development of LightTPD and / or NGINX as fast, efficient and FREE webserver alternatives.
So going back to my original question, I wonder if it’s possible to configure the server so that the static html pages are served by other than Apache. I don’t mean the entire server running Nginx or Lighty, but a “normal” server with Apache and Nginx or Lighty as a proxy for serving content and the static html pages.
And please, please, someone publish how to get WordPress permalinks to work under Lighty or NGINX, that would be a great start towards dropping LiteSpeed.
- The topic ‘Serving cached static html pages with LightTPD or NGINX?’ is closed to new replies.