petermolnar

WARNING The development of WP-FFPC had been put on hold. 
If you need new features, please send code and pull requests to <a href="https://github.com/petermolnar/wp-ffpc" rel="nofollow ugc">WP FFPC @ Github</a>.
A short why: I developed this plugin in 2010 to support my own site. Right now, as it is, it’s working on a few sites I still maintain for friends and since I don’t need any additional features, I’m not planning to extend it with things I have no real use of. During the past years I’ve received some heartwarming donations – unfortunately the amount never came close to consider the project financially beneficial. I removed the donation links and put it on hold for now.
WP-FFPC is a cache plugin for <a href="https://wordpress.org/" title="WordPress" rel="ugc">WordPress</a>. 
It works with any webserver, including, but not limited to, apache2, lighttpd, nginx.
It can be configured together with <a href="http://NGiNX.org" title="NGiNX" rel="nofollow ugc">NGiNX</a> but use <a href="http://nginx.org/en/docs/http/ngx_http_memcached_module.html" title="memcached plugin" rel="nofollow ugc">memcached plugin</a> directly from the webserver, bypassing PHP.
<h4>Requirements</h4>
This plugin does not kick in right after activation. You have to adjust the setting in Settings -> WP-FFPC and save the settings.*
<ul>
<li>WordPress >= 3.0</li>
<li>at least one of the following for storage backend:
<ul>
<li>memcached with <a href="http://php.net/manual/en/book.memcached.php" title="Memcached" rel="nofollow ugc">PHP Memcached</a> > 0.1.0</li>
<li>memcached with <a href="http://php.net/manual/en/book.memcache.php" title="Memcache" rel="nofollow ugc">PHP Memcache</a> > 2.1.0</li>
<li><a href="http://php.net/manual/en/book.apc.php" title="APC" rel="nofollow ugc">APC</a></li>
<li><a href="http://pecl.php.net/package/APCu" title="APC User Cache" rel="nofollow ugc">APCu</a></li>
</ul>
</li>
<li>PHP 5.3+ is really highly recommended, see “Known issues”</li>
</ul>
<h4>Known issues</h4>
<ul>
<li>errors will not be displayed on the admin section if PHP < 5.3, only in the logs. This is due to the limitations of displaying the errors ( admin_notices is a hook, not a filter ) and due to the lack of proper anonymus functions in older PHP.</li>
<li>If you’re using PHP 5.4+ avoid the APC backend: the plugin with that setup can even make your site slower. Please use APCu or memcached in this case.</li>
</ul>
<h4>Features:</h4>
<ul>
<li>various backends
<ul>
<li>memcached with <a href="http://php.net/manual/en/book.memcached.php" title="Memcached" rel="nofollow ugc">PHP Memcached</a></li>
<li>memcached with <a href="http://php.net/manual/en/book.memcache.php" title="Memcache" rel="nofollow ugc">PHP Memcache</a></li>
<li><a href="http://php.net/manual/en/book.apc.php" title="APC" rel="nofollow ugc">APC</a></li>
<li><a href="http://pecl.php.net/package/APCu" title="APC User Cache" rel="nofollow ugc">APCu</a></li>
</ul>
</li>
<li>cache exclude options ( home, feeds, archives, pages, singles; regex based url exclusion )</li>
<li>minor Woocommerce support</li>
<li>(optional) cache for logged-in users</li>
<li>404 caching</li>
<li>canonical redirects caching</li>
<li>Last Modified HTTP header support (for 304 responses)</li>
<li>shortlink HTTP header preservation</li>
<li>pingback HTTP header preservation</li>
<li>talkative log for <a href="https://codex.wordpress.org/WP_DEBUG" title="WP_DEBUG" rel="nofollow ugc">WP_DEBUG</a></li>
<li>multiple memcached upstream support</li>
<li>precache ( manually or by timed by wp-cron )</li>
<li>varying expiration time for posts, taxonomies and home</li>
<li>(warning: untested since WordPress 3.8) WordPress Network support
<ul>
<li>fully supported domain/subdomain based WordPress Networks on per site setup as well</li>
<li>will work in Network Enabled mode only for subdirectory based Multisites ( per site settings will not work in this case )</li>
</ul>
</li>
</ul>
Many thanks for donations, contributors, supporters, testers & bug reporters:
Harold Kyle, Eric Gilette, doconeill, Mark Costlow, Jason Miller, Dave Clark, Miguel Clara, Anton Pelešev, Firas Dib, CotswoldPhoto, tamagokun, Many Ayromlou, mailgarant.nl, Christian Rößner, Ameir Abdeldayem, Alvaro Gonzalez, Meint Post, Knut Sparhell, Christian Kernbeis, Gausden Barry, Maksim Bukreyeu, Lissome Hong Kong Limited, Gabriele Lauricella, 7th Veil, LLC, Julia Harsch, Grant Berntsen, Jorgen Ilstad, Cinema Minima for Movie Makers Worldwide

WP-FFPC

One of the best plugins for caching, simple and fast performance.

One of the best

Reduced loading time of Ajax queries by 30%!

Excellent plugin!

A fast, memory based full page cache plugin supporting APC or memcached.

Daniel Bachhuber

Pantheon Systems

stevector

For sites concerned with high traffic, speed for logged-in users, or dynamic pageloads, a high-speed and persistent object cache is a must. WP LCache improves upon Memcached and Redis object cache implementations by using APCu, PHP’s in-memory cache, in a way that’s compatible with multiple web nodes. Under the hood, WP LCache uses <a href="https://github.com/lcache/lcache" rel="nofollow ugc">LCache</a>, a library that applies the tiered caching model of multi-core processors (with local L1 and central L2 caches) to web applications.
Note: WP LCache development is currently on hold, and not recommendated for production use, due to an <a href="https://github.com/lcache/wp-lcache/issues/138" rel="nofollow ugc">issue with APCu cache fragmentation</a>. <a href="https://wordpress.org/plugins/wp-redis/" rel="ugc">WP Redis</a>, also maintained by Pantheon, is a great alternative.
WP LCache is faster than other object cache implementations because:
<ul>
<li>By using APCu, which is in-memory, WP LCache uses the fastest possible persistent object cache backend and avoids costly network connections on every request. When using a Memcached or Redis-based persistent object cache where Memcached or Redis is on a different machine, the millisecond cost of each cache hit can add up to seconds of network transactions on every request.</li>
<li>By incorporating a common L2 cache, WP LCache synchronizes cache data between multiple web nodes. Cache updates or deletes on one node are then applied to all other nodes. Without this synchronization behavior, APCu can’t be used in server configurations with multiple web nodes because the cache pool is local to the machine.</li>
</ul>
Still not convinced? WP LCache includes features that no one else has:
<ul>
<li>Cache groups are handled natively, meaning you can delete an entire group of keys with <code>wp_cache_delete_group()</code>.</li>
<li>WordPress’ alloptions cache is sharded into distinct keys, mitigating cache pollution on high traffic sites. <a href="https://core.trac.wordpress.org/ticket/31245" rel="nofollow ugc">Read #31245</a> for all of the gory details.</li>
</ul>
Read the installation instructions, then install WP LCache from <a href="https://wordpress.org/plugins/wp-lcache/" rel="ugc">WordPress.org</a> or <a href="https://github.com/lcache/wp-lcache" rel="nofollow ugc">Github</a>.
Go forth and make awesome! And, once you’ve built something great, <a href="https://github.com/lcache/wp-lcache/issues" rel="nofollow ugc">send us feature requests (or bug reports)</a>.
<h3>Contributing</h3>
The best way to contribute to the development of this plugin is by participating on the GitHub project:
https://github.com/lcache/wp-lcache
Pull requests and issues are welcome!
You may notice there are two sets of tests running, on two different services:
<ul>
<li>Travis CI runs the <a href="https://phpunit.de/" rel="nofollow ugc">PHPUnit</a> test suite in a variety of environment configurations (e.g. APCu available vs. APCu unavailable).</li>
<li>Circle CI runs the <a href="http://behat.org/" rel="nofollow ugc">Behat</a> test suite against a Pantheon site, to ensure the plugin’s compatibility with the Pantheon platform.</li>
</ul>
Both of these test suites can be run locally, with a varying amount of setup.
PHPUnit requires the <a href="https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/" rel="nofollow ugc">WordPress PHPUnit test suite</a>, and access to a database with name <code>wordpress_test</code>. If you haven’t already configured the test suite locally, you can run <code>bash bin/install-wp-tests.sh wordpress_test root '' localhost</code>. You’ll also need to install and configure APCu in order to run the test suite against APCu.
Behat requires a Pantheon site. Once you’ve created the site, you’ll need <a href="https://github.com/pantheon-systems/terminus#installation" rel="nofollow ugc">install Terminus</a>, and set the <code>TERMINUS_TOKEN</code>, <code>TERMINUS_SITE</code>, and <code>TERMINUS_ENV</code> environment variables. Then, you can run <code>./bin/behat-prepare.sh</code> to prepare the site for the test suite.

WP LCache

Supercharge your WP Object Cache with LCache, a persistent, performant, and multi-layer cache library.

WP-FFPC vs WP LCache