Mohammed Kassem

MAKcubes | Cache Nuke is a lightweight administrative utility designed to help site administrators clear WordPress core caching mechanisms during troubleshooting or maintenance.
The plugin focuses on: 
– Clearing WordPress transients. 
– Flushing the WordPress object cache when available. 
– Triggering cache purge hooks for some popular caching plugins, when those plugins are installed and expose public purge actions.
This plugin does not communicate with external services, does not include tracking or analytics, and runs only for authorized administrators.
<h3>License</h3>
This plugin is licensed under the GPLv2 or later.

MAKcubes | Cache Nuke

A lightweight utility plugin to clear WordPress core caches such as transients and object cache.

Vladimir Kolesnikov

The plugin implements object level persistent caching and can be used instead of the built in WordPress <code>WP_Object_Cache</code>. 
Unlike WP Super Cache, Hyper Cache and other plugins, WP File Cache does not cache the entire page; instead, it caches the data WordPress explicitly asks it to cache (using <code>wp_cache_xxx()</code> API functions). 
Although this means that the performance will be less than with, say, WP Super Cache, all your pages remain dynamic. 
WP File Cache won’t help you much if the plugins or theme you are using do not use WordPress Cache API. This is by design, since the plugin tries to play nice. However, for most WordPress installations this will not be critical.
WP File Cache significantly reduces the load from your database. Say, my blog’s home page without the plugin executes 24 queries (0.02403 sec); with the plugin enabled, only 4 queries (0.00188 sec). 
Unlike DB Cache/DB Cache Reloaded, the plugin will work in the Admin Panel and supports all plugins that use WordPress Cache API.
Please note that WP File Cache shifts the load from your database to your disk/file system and if Disk I/O is a bottleneck, file based caches will not help you.
To get the maximum cache performance, please disable <code>open_basedir</code> in your <code>php.ini</code> — it really slows the things down.
WARNING: chances are that the plugin will not work when PHP safe mode is enabled and web server is operated by a different user than owns the files.
<h3>wp-config.php Magic Constants</h3>
There is one magic constant, <code>WP_FILE_CACHE_LOW_RAM</code>. When <code>ini_get('memory_limit') - memory_get_usage()</code> becomes less than <code>WP_FILE_CACHE_LOW_RAM</code>, caching gets partially disabled. 
This means that the data that are available in the memory cache will still be used but no reads from the files will be performed. This can be useful when you get Out of Memory errors in <code>class.FileCache.php</code>.
By default this feature is turned off but you can enable it with defining
<pre><code>define('WP_FILE_CACHE_LOW_RAM', '4M');
</code></pre>
Repleace <code>4M</code> with your value.
<h3>Deactivation/Removal</h3>
<ol>
<li>Please make sure that <code>wp-content</code> directory is writable by the web server: the plugin will need to delete <code>object-cache.php</code> from it.</li>
<li>Deactivate/uninstall the plugin through the ‘Plugins’ menu in WordPress.</li>
<li>Please verify that <code>wp-content/object-cache.php</code> file was removed.</li>
</ol>

MAKcubes | Cache Nuke vs WP File Cache