Automattic

Mark Jaquith

Mohammad Jangda

Andy Skelton

Yoav Farhi

vnsavage

orensol

<p>Batcache uses Memcached to store and serve rendered pages. It can also optionally cache redirects. It’s not as fast as Donncha’s WP-Super-Cache but it can be used where file-based caching is not practical or not desired. For instance, any site that is run on more than one server should use Batcache because it allows all servers to use the same storage.</p>
<p>Development testing showed a 40x reduction in page generation times: pages generated in 200ms were served from the cache in 5ms. Traffic simulations with Siege demonstrate that WordPress can handle up to twenty times more traffic with Batcache installed.</p>
<p>Batcache is aimed at preventing a flood of traffic from breaking your site. It does this by serving old pages to new users. This reduces the demand on the web server CPU and the database. It also means some people may see a page that is a few minutes old. However this only applies to people who have not interacted with your web site before. Once they have logged in or left a comment they will always get fresh pages.</p>
<p>Possible future features:</p>
<ul>
<li>Comments, edits, and new posts will trigger cache regeneration</li>
<li>Online installation assistance</li>
<li>Configuration page</li>
<li>Stats</li>
</ul>


Batcache

Batcache uses Memcached to store and serve rendered pages.

Hristo Pandjarov

getClouder

<p>The main functionality of NGINX Cache Optimizer is to purge your NGINX cache whenever your content updates. For example, when you create a new post, someone comments your articles, etc. In addition to that, if you have a working Memcached service on your server, the plugin will allow you to easily configure and enable WordPress to use it.</p>
<h4>Requirements</h4>
<p>In order to work correctly, this plugin requires that your server meets the following criteria:</p>
<ul>
<li>NGINX configured to cache dynamic content</li>
<li>Writable permissions for the user executing PHP scripts on the NGINX cache folder</li>
</ul>
<h3>Configuration</h3>
<h4>Dynamic Cache Settings</h4>
<ul>
<li>nginx Cache Directory – </li>
<li>Dynamic Cache ON/OFF – </li>
<li>AutoFlush Cache ON/OFF – </li>
<li>Purge Cache – Manually purge all cached data from the NGINX cache</li>
</ul>
<h4>Exclude URLs From Dynamic Caching</h4>
<p>This field allows you to exclude URLs from the cache. This means that if you need certain parts of your site to be completely dynamic, you need to add them into this list. Type in the last part of the URL that you want to be excluded. For example, if you type in ‘url’, then ‘/path/to/url/’ will be excluded but ‘/path/to/’ and ‘/path/to/url/else/’ won’t.</p>
<h4>Memcached Settings</h4>
<ul>
<li>Memcached Instance IP Address – The IP address of the Memcached service. By default, it’s set to 127.0.0.1.</li>
<li>Memcached Instance Port – The port on which Memcached is running. By default, memcached uses port: 11211</li>
<li>Enable Memcached – this is the main Memcached support switch. Once you enter your Memcached server IP address and port, you need to actually enable it by setting this option to ON.</li>
</ul>


NGINX Cache Optimizer

The main functionality of NGINX Cache Optimizer is to purge your NGINX cache whenever your content updates. For example, when you create a new post, s …

Batcache vs NGINX Cache Optimizer