Dan Collis-Puro

Need for Speed?
This plugin handles the wordpress/php side of a statically cached nginx-fronted wordpress (or wordpress mu) site. It makes WordPress emit an “X-Accel-Expires: 0” header when a user is logged in or has taken actions that should cause them to get a customized page on your frontend. This – along with the nginx configuration below – will ensure logged-in users aren’t impacted by your static nginx cache.
Why would you want to statically cache wordpress with <a href="http://www.nginx.org" rel="nofollow ugc">nginx?</a>
<ul>
<li>INSANE performance. Hardware that could generate 6 pages / second can now generate many thousands.</li>
<li>Low resource usage. Even on very busy servers, nginx uses only a handful of RAM.</li>
<li>Unobtrusiveness. You plop nginx in front of wordpress and that’s pretty much it. This plugin (and nginx) is all you need to make your site digg- and slashdot- proof.</li>
<li>Stability. Nginx is rock solid.</li>
<li>Faster is better. All the web gurus agree – visitors like faster sites, even when the differences are slight.</li>
<li>Do more with less. Using a frontend proxy lets you keep your heavy wordpress apaches lightly loaded, letting you handle more concurrent connections and use less RAM.</li>
</ul>
We’ve been using a caching nginx proxy at the fairly busy <a href="http://blogs.law.harvard.edu" rel="nofollow ugc">blogs.law.harvard.edu</a> since September, 2009. The results have been dramatic: we’ve halved the amount of RAM we need, doubled our outgoing network throughput (nginx is fast!) and have had essentially no significant load spikes.
Drawbacks
There are a few.
<ul>
<li>Plugins that rely on php code running on each page view won’t work properly. This is similar to wp-supercache or any of the other static caching plugins. Stats, image rotation, etc. You should implement these features via javascript or third-party services, depending. </li>
<li>You need to install and configure an nginx frontend proxy – but see the “installation” tab. It’s really not that hard.</li>
</ul>
Notes
<ul>
<li>It is completely harmless to install and activate this plugin before you’ve got the nginx side set up.</li>
<li>YOU MUST keep this plugin activated as long as you’ve got an nginx frontend proxy active – otherwise, you’ll end up caching too much of your site, and authenticated users won’t see customized pages.</li>
<li>This plugin helps speed up access for authenticated users mainly because it makes all other traffic a negligible resource drain. I suggest installing <a href="http://php.net/manual/en/book.apc.php" rel="nofollow ugc">apc</a> (or another opcode cache) and – alternatively – a wordpress object cache. Definitely install an opcode cache – leave the object cache for later. You may find you don’t need it!</li>
</ul>
<h3>The Future</h3>
This plugin could be set up to allow you to manage caching policies entirely from a wordpress control panel. We’d do this by manipulating the timeout in the “X-Accel-Expires” header based on the type of resource that’s been requested.
It’d be nice to de-cache when pages change via some call from the backend to the nginx frontend.

WordPress Nginx proxy cache integrator

Enables your blog to work properly with an nginx frontend static proxy cache. ASTRONOMICAL performance is yours!

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.

WordPress Nginx proxy cache integrator vs WP-FFPC