Comments on: Wordpress Lighttpd vs. Apache Httpd Perfomance Test

By: How To Run Lighttpd with Wordpress! | Web Server Hacks Blog – Hacks for Dedicated/VPS Servers, SSH, and Plesk

Wed, 14 Oct 2009 08:52:43 +0000

[...] Home About RSS Follow @WebServerHacks on Twitter « Wordpress Lighttpd vs. Apache Httpd Perfomance Test [...]

By: admin

admin — Wed, 14 Oct 2009 07:14:54 +0000

Hmmm… I believe I have set it up correctly, the pages have been verified as compressed gzipped files so I don’t think that’s the issue here, there’s clearly no performance improvement in using either of the methods but yes, they do way better than Apache for sheezy.

Let me also add that load was increased on a VPS server, where resources are very limited. However same tests on a raw quad-core dedicated server with 8GB of memory yielded almost no load.

By: chris

chris — Wed, 23 Sep 2009 05:11:18 +0000

hi — no offense, but it looks like you’re not setting up your blogs correctly with supercache and the lighttpd Lua mod_magnet script. the whole point is that the mod_magnet script turns any potential PHP/wordpress calls into a plain ol’ static file requests, which should be ridiculously fast for lighttpd to return.

if you’re getting only 12 reqs/sec and high load averages, then your magnet setup isn’t finding the supercache’d page (index.html.gz, index.html etc). if you’ve set things up correctly, you shouldn’t see your PHP processes churning at all, and should basically have no noticeable load increase.

my ab results for a blog i have set up with the asteriosk.gr method can do 100s of reqs/sec (running locally—not measuring network times from my desktop to the server). you have to remember to set up the rewrite rule in your lighttpd config to send calls for the index page to index.php. also to test gzip you need to add -H “Accept-Encoding: gzip,deflate” to your ab options.