Home > General Articles > WordPress Super Cache on lighttpd

WordPress Super Cache on lighttpd

August 2nd, 2009 Leave a comment Go to comments

While trying to speed up Select Articles, I got stuck, torn in between WP Super Cache and lighttpd. Already we at Saturn are using lighttpd on several dedicated servers, and know the potential and benefit of having this over Apache though the flexiblity of having a perdirectory configuration at the programmers choice was a big question. A quick search on the Google landed me to a technical blog, notepad and personal web page by Asterios Katsifodimos.

Trying to get WP Super Cache & WordPress working on my fast lighttpd server, I came into problems, mainly because of lighttpd’s lack of (Apache’s version of) the mod_rewrite module. The static files that were created from the cache were not statically served from wordpress. The problem is that in order to use them, the PHP fcgi was called for each request. So, why would we have to call PHP every time that a file can be completely statically provided by the web server?

Read the rest of his version Installing WP Super Cache with lighttpd

  1. August 19th, 2009 at 15:11 | #1

    Ive abandoned using just Lighttpd and (mainly due to the lack of mod_rewrite) and now use Apache to process to the PHP and a Lighttpd server to serve the static content – I’ve got to say i really like it. I get all the benefit of Apache with all the features and low memory footprint of Lighttpd.

    I took a slightly different approach to caching and simply wrapped the index.php file in a APC cache I created (details can be found http://www.idontplaydarts.com/2009/08/caching-wordpress-as-static-html-using-apc/) – its not ideal for every user but if its a single user blog its pretty neat.

  1. No trackbacks yet.

ten + = eighteen