variable performance

Hi Nic,

Initial page load: the plugin only utilize cache after the first load of the page.
Could you be a littlebit more specific on the variability on the cases you tested? Logged in, visitor only, etc.

Also, if you have any idea what could be made better, I’d welcome it.

Cheers,
Peter

Nic,

WP-FFPC and HyperCache work in different scenarios. Even though, I haven’t used HyperCache, I noticed that it is a file-based caching system. So, it is expected to work in most hosting environment without any specific issues. On the other hand, WP-FFPC uses either APC or Memcached. I never used APC with WP-FFPC. However, with Memcached, it works for me on an Nginx server. APC is very efficient than any other caching layers, IMO. However, making it to work on a particular host is tricky. You can see many issues on other plugins that use APC too. A host is where to ask help in such a situation, rather than a plugin author who is mostly concerned about bugs, features, etc.

Yes Hyper Cache is a file based caching system Pothi, however WP-FFPC is based on Hyper Cache so I assumed that it would be creating static pages also (although I did not see any) as well as using the PHP opcode cache (the two are different and can be combined).

Peter, can you confirm is static page are generated / cached and where they are stored.

Hi Nic,

It’s not based on Hyper Cache anymore. It was, using mostly concept until 0.6.1, version 1.0 is nearly a complete refactor, leaving most of the previous codebase behind ( even the readme.txt related text is changed that mentions Hyper Cache )

There are no classic files generated: the output of WordPress is saved as string in either APC user container or in memcached. For info on APC entries & stats, please read ( for example ) this arcticle: https://www.electrictoolbox.com/apc-php-cache-information/

Hi Nic,

Is there any update on this topic? If not, I’ll be closing it tomorrow.

Cheers,
Peter

Hi Peter,

I may test WP-FFPC again (didn’t have / give it enough time initially), however I do have a working, stable and fast solution with;

apache + nginx (as proxy / cache)
w3 total cache (opcode disabled) – handles CDN rewrites
tribe cache (for opcode)

I’ve dramatically reduced server load now with static files served by nginx via proxy, CDN delivering other heavy static files and leaving apache and opcode to deal with the rest.

Do you think WP-FFPC could improve on that ?

Hi Nic,

This setup would definately need testing but the cache plugin ( and I mean any kind of ) would only make a difference at a fairly high load.
If you have numerous hits/second than yes, it should make difference but it could be just a slight one.

Thank you for responding Peter although I’m not sure I would agree as it would depend on how that load is generated – from real visitor traffic / activity or due to site / server that is not tuned to deliver performance (depending on available HW resources) – however I will give it another test when I have the chance.

Half year old thread, possible sorted out by now.