Comments on: Caching wordpress as static HTML using APC

By: Dirty Wordpress APC caching - Florent Clairambault

Dirty Wordpress APC caching - Florent Clairambault — Sat, 13 Feb 2010 08:10:32 +0000

[...] I had the brilliant idea to put everything in an APC cache, someone had the same [...]

By: Florent Clairambault

Florent Clairambault — Fri, 12 Feb 2010 20:49:35 +0000

Very good idea. I had exactly the same and wanted to do the same thing. Just wanted to tell you that : md5($_SERVER['REQUEST_URI'] .serialize($_GET)) will change at the same frequency as md5($_SERVER['REQUEST_URI']) because the REQUEST_URI actually contains the GET arguments.

I think you can implement it more properly, give a longer timeout and clean everything as soon as a comment is posted or a new post is added.

By: Phil

Phil — Sun, 17 Jan 2010 22:18:38 +0000

Its probably that dreamhost doesnt support APC (the APC cache is an extension of PHP), do a phpinfo(); and see if you can see a heading for APC – if its not there then its not being support by Dreamhost.

By: Eckhard

Eckhard — Sun, 17 Jan 2010 02:39:41 +0000

Fatal error: Call to undefined function apc_fetch() in /home/xxxxxxx.com/index.php on line 5
unfortunately with the WP- 2.9.1 on dreamhost it is not working well
any idea what to change??
thanks

By: Phil

Phil — Wed, 04 Nov 2009 10:15:43 +0000

My method is somewhat of a bodge – I only have 150 pages on my site which means that everything will easily fit within 6mb of memory preventing page flushes. You are quite right – if you know you can’t fit everything in memory, dont use my crude method. Pre-generating the page and storing it on disk would be a much better option.

Look forward to seeing your wordpress cache plugin – hopefully it’ll be a little more sophisticated than my method

By: php trivandrum

php trivandrum — Wed, 04 Nov 2009 03:47:37 +0000

Caching pages with in memory caches can improve performance but you will exhaust the reserved memory and page flushes will occur, actually reducing in performance in a realtime scenario.

But for heavily customized homepages, with loads of visitors as witten http://www.php-trivandrum.org/general-articles/speeding-up-wordpress-home-page/, the partial data caching in ram disk without any in memory cache would be at par. Here the home page is only cached.

I am working on a plugin for word press which will help out doing this more decently.

By: Phil

Phil — Wed, 23 Sep 2009 09:52:23 +0000

Yeah, i agree totally, if you used a static file the results would be much faster (quite how much faster I’m not sure) and it would prevent the call to APC/PHP. In my case APC will do as it appears that my upstream connection gets saturated before the calls to PHP become an issue.

I’ll give the static file method a try (probably sometime this week) and see how the results compare

By: chris

chris — Wed, 23 Sep 2009 05:26:51 +0000

these are pretty good numbers, but isn’t the whole point of supercache and static file generating is so you avoid the trip to PHP in the first place? handling a ton of requests via PHP/FastCGI vs. having lighttpd/Apache return the static file with one stat() call to check if it exists, it seems like the static file method is going to be tons faster.

By: Phil

Phil — Tue, 18 Aug 2009 08:54:29 +0000

Let hope comments still work with this caching…