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!

Aurélien LWS

This plugin, created by <a href="https://www.lws.fr" rel="nofollow ugc">LWS</a> help to automatically manage your LWSCache purge when you edit your pages, post, messages…
It provide a way to purge all your LWSCache.
This plugin works only on servers using the LWSCache system. This cache is pre-installed with Classic shared <a href="https://www.lws.fr/hebergement_web.php" rel="nofollow ugc">web hosting</a>, <a href="https://www.lws.fr/hebergement_wordpress.php" rel="nofollow ugc">WordPress hosting</a> and soon <a href="https://www.lws.fr/hebergement-cpanel.php" rel="nofollow ugc">cPanel hosting</a> from LWS.
The loading speed of your site is crucial to its success. The more visitors your site has, the more RAM and CPU memory the system uses. The page is loaded slowly. So you need a cache system to avoid reloading the page when it is not necessary.
In addition, the site’s page load speed is used in Google’s ranking algorithm. So caching plugins that can improve load times will improve your SEO ranking. Low rankings, and therefore insufficient exposure, often do not allow you to make a living from your website. The loading time of most websites is less than three seconds. Beyond that, many users have already left the page.
The LWS Cache tool is a system designed and developed by LWS. It optimize the loading performance of your website through the use of advanced caching mechanisms, configured at the server level. The tool uses the technologies provided by NGINX.
<h4>Functioning</h4>
When LWS Cache is enabled, a cache server is introduced between the visitor and the web server. 
The aim is to reduce the number of script executions required. For that it keeps the result of the execution in memory for future requests requiring the same response. This means that the same script is no longer executed several times to achieve the same result.
Thus, we eliminate the waiting time of the script execution on the page loading time. At the same time, we save the resources used during the script execution.
<ul>
<li>The visitor requests the page from the web server. Example: index.php. LWS Cache checks if the page has already been generated and stored in the cache</li>
</ul>
If yes, the page is returned directly to the visitor without the need to access the web service and without executing the script
If not, the page is requested to be generated on the web service as a result of the script execution (PHP, NodeJS, Perl, Ruby, …).
<ul>
<li>Once the page is generated, LWS Cache determines if the page can be cached (via headers, URL, …)</li>
</ul>
If yes, the page is saved in the cache and returned to the visitor
If not, the page is saved in the microcache (short-lived cache) and returned to the visitor
<h4>Managing LWS Cache with the plugin</h4>
The WordPress LWS Cache plugin allows you to automatically purge the cache of your pages when you modify them or when you add/approve comments.
To manage the plugin, once connected to your WordPress administration console, go to the “Settings” menu and then “LWS Cache”.
From the settings page, you can enable/disable automatic emptying. You can define when to automatically empty the LWS Cache and completely purge the cache.
A button for emptying the entire cache can be found anywhere in the WordPress admin console (in the quick access bar at the top of the screen).
<h4>Key Features</h4>
Several settings are available to manage your LWS Cache, you can enable or disable these settings:
<ul>
<li>
Automatic purge
</li>
<li>
Home Page Purge (when a post is modified or added, when a published post is trashed)
</li>
<li>
Purge Post/Page/Custom Post Type (when a post is published, when a comment is approved/published, when a comment is unapproved/deleted)
</li>
<li>
Purge Archives (date, category, tag, author, custom taxonomies)
</li>
<li>
Purge all cache
</li>
</ul>

LWSCache

This plugin lets you manage and automatically purge your hosting's LWSCache whenever you edit your website's content

WordPress Nginx proxy cache integrator vs LWSCache