Emre Vona

<h4>Official Website</h4>
You can find more information on our website (<a href="https://www.wpfastestcache.com/" rel="nofollow ugc">wpfastestcache.com</a>)
Welcome to the page of the WP Fastest Cache plugin, a WordPress cache plugin developed to speed up WordPress sites.
In today’s world where every second counts, optimizing your website’s performance is very important. Meet WP Fastest Cache, your caching plugin that you can use to speed up WordPress websites. 
Optimize the performance of your website with WP Fastest Cache. Improve Google PageSpeed, Core Web Vitals, GTmetrix and Pingdom score with our wp cache plugin.
In addition, page speed is a ranking factor in Google’s search algorithm. Therefore, using cache plugins helps improve your SEO ranking. Our WordPress optimization plugin not only accelerates your site but also boosts SEO rankings.
<h4>Features</h4>
<ol>
<li>Mod_Rewrite which is the fastest method is used in this plugin</li>
<li>All cache files are deleted when a post or page is published</li>
<li>Admin can delete all cached files from the options page</li>
<li>Admin can delete minified css and js files from the options page</li>
<li>Block cache for specific page or post with Short Code</li>
<li>Cache Timeout – All cached files are deleted at the determinated time</li>
<li>Cache Timeout for specific pages</li>
<li>Enable/Disable cache option for mobile devices</li>
<li>Enable/Disable cache option for logged-in users</li>
<li>SSL support</li>
<li>CDN support – Effortlessly enhance website speed and performance with seamless CDN integration, supporting Bunny CDN, Cloudflare, and various other leading CDN providers. CDN integration modifies the URLs of static resources, enabling these assets to be served from your CDN service provider</li>
<li>Cloudflare support – Cloudflare integration triggers the clearing of the cache on Cloudflare through API when a cache purge is initiated. As a result, WP Fastest Cache and Cloudflare operate seamlessly in tandem</li>
<li>Preload Cache – Create the cache of all the site automatically</li>
<li>Exclude pages and user-agents</li>
<li>WP-CLI cache clearing</li>
<li>Proxy Cache – Varnish Cache Integration to clear proxy cached content automatically when the cache created by WP Fastest Cache is cleared</li>
</ol>
<h4>Performance Optimization</h4>
WP Fastest Cache is not only a wp cache plugin but also a speed optimization wordpress cache plugin. There are many features such as Minify Html, Minify Css, Enable Gzip Compression, Leverage Browser Caching, Add Expires Headers, Combine CSS, Combine JS, Disable Emoji.
<ol>
<li>Page Caching – Page caching feature generates and store static HTML files from your dynamic WordPress blog to reduce initial server response time, and improving page load time. Page cache and caching play a critical role in improving website speed and overall web performance. By storing frequently accessed data, effective caching reduces server workload and significantly improves cache performance, allowing pages to be delivered faster to users. This optimization directly lowers load time and enhances page speed, resulting in a smoother user experience and better SEO.</li>
<li>Minify Html – Using an HTML minifier is an effective way to reduce HTML size and optimize HTML by removing unnecessary spaces, comments, and line breaks. A smaller HTML file helps reduce page size, which directly improves page speed and leads to a faster website experience for users. By focusing on web performance optimization, optimized HTML allows browsers to load and render pages more efficiently, helping to improve website speed, lower bandwidth usage, and deliver better overall performance across all devices</li>
<li>Minify Css – CSS minify techniques play a crucial role in modern web development by reducing unnecessary characters through a reliable css minifier. With effective css compression, developers can compress CSS files and apply proper css minification to optimize CSS for production environments. This approach helps reduce CSS file size, which directly contributes to improve website speed and overall css performance optimization. As part of a broader page speed optimization strategy, these practices significantly enhance website performance optimization and lead to better website loading performance, especially on mobile and low-bandwidth connections</li>
<li>Enable Gzip Compression – Reduce the size of files sent from your server to increase the speed to which they are transferred to the browser</li>
<li>Leverage browser caching – Browser cache plays a critical role in how efficiently a web browser cache stores static resources like images, stylesheets, and scripts, directly impacting page load speed. By allowing returning visitors to load files from their local browser cache instead of downloading them again, websites can significantly reduce server requests and improve website speed. Properly configured browser caching not only creates a faster and smoother user experience but also helps lower bandwidth usage and enhance overall site performance</li>
<li>Combine CSS – Reduce number of HTTP round-trips by combining multiple CSS resources into one</li>
<li>Combine JS – Combining JavaScript files is a core technique in javascript optimization and js optimization, especially when the goal is to reduce requests and improve page load speed. By combine js assets or combine javascript files into a single bundle, developers can streamline how scripts are delivered to the browser. Whether you call it js combine or javascript combine, the idea is the same: fewer HTTP requests mean faster performance. Similarly, approaches that merge js or merge javascript—also known as js merge or javascript merge—help eliminate overhead caused by loading multiple separate files. When done correctly, combining and merging scripts leads to cleaner delivery, better caching, and noticeably faster websites</li>
<li>Disable Emoji – You can remove the emoji inline css and wp-emoji-release.min.js</li>
</ol>
<h4>Premium Performance Optimization</h4>
The free version is enough to speed up your site but in the premium version there are extra features such as Mobile Cache, Widget Cache, Minify HTML Plus, Minify CSS Plus, Minify JS, Combine JS Plus, Defer Javascript, Optimize Images, Convert WebP, Database Cleanup, Google Fonts Async, Lazy Load and Delay JS for super fast load times.
<ol>
<li>Mobile Cache</li>
<li>Widget Cache</li>
<li>Minify HTML Plus</li>
<li>Minify CSS Plus</li>
<li>Minify Javascript – Minify JS is a core step in web performance optimization because js minify techniques remove unnecessary characters, comments, and whitespace, making files smaller and faster to load. Through proper javascript minification, developers can compress JavaScript assets and significantly reduce transfer size, which directly supports effective js optimization and overall javascript optimization strategies. When combined with caching and code splitting, minified scripts help improve website speed, lower bandwidth usage, and enhance user experience. As a result, page speed optimization becomes easier to achieve, leading to faster render times and better search engine rankings.</li>
<li>Combine JS Plus</li>
<li>Defer Javascript – Eliminate render-blocking JavaScript resources. Consider delivering critical JS inline and deferring all non-critical JS</li>
<li>Optimize Images – Optimized images load faster and consume less cellular data. Looking for an easy image compressor? Our tool lets you compress images instantly, including Compress JPEG and Compress PNG options. Enjoy fast image compression to reduce image size without losing quality. Perfect for quick image optimization with a smart image optimizer designed for all your needs.</li>
<li>Convert WebP – Serve images in next-gen formats. Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. A fast and reliable WebP converter helps you convert to WebP in seconds. Whether you need a WebP convert tool, a JPG to WEBP Converter, PNG to WEBP Converter, or a simple image to WebP option, you can easily optimize your images. Quickly handle JPG to WEBP, PNG to WEBP, jpg convert to webp, and png convert to webp tasks to reduce file size and improve web performance.</li>
<li>Database Cleanup – To keep your system running smoothly, it’s important to clean database structures regularly and ensure you clean DB records that are no longer needed. A database cleaner is essential for effective database cleaning and long-term database optimization. By removing unused entries and organizing data efficiently, you can significantly improve database performance and speed up database operations. Modern db cleaner tools automate the entire db cleaning process, helping developers maintain fast, reliable, and scalable systems. The Database Cleanup feature clears out all of the garbage datas such as post revisions, trashed posts & pages, comments from trash & spam, trackbacks and pingbacks, transient options, orphaned post meta, comment meta, user meta, term meta, and term relationship etc.</li>
<li>Google Fonts Async</li>
<li>Lazy Load – Lazy loading technique improve page speed and overall website loading time by loading content only when it is needed. Using lazy load images, lazy loading images, lazy load videos, and lazy load iframe helps reduce initial load size, enhances web performance, and delivers a smoother user experience. When implemented correctly, these methods make it easier to optimize website performance, lower bandwidth usage, and ensure faster, more efficient page delivery for both users and search engines.</li>
<li>Delay JS – The Delay JavaScript feature helps reduce the ‘Reduce unused JavaScript’ warning in the Google PageSpeed Insights tool</li>
</ol>
<h4>Information</h4>
It is very inconvenient to use multiple caching plugins at the same time. That’s why you need to disable plugins such as LiteSpeed Cache, WP-Optimize, W3 Total Cache, WP Super Cache, SiteGround Optimizer, Breeze while using WP Fastest Cache.
WP Fastest Cache is compatible with most popular plugins such as Contact Form 7, Yoast SEO, Elementor Website Builder, Classic Editor, Akismet Spam Protection, WooCommerce, Contact Form by WPForms, Really Simple SSL, All-in-One WP Migration, Yoast Duplicate Post, Wordfence Security – Firewall & Malware Scan, WordPress Importer, UpdraftPlus WordPress Backup Plugin, MonsterInsights, All in One SEO, WP Mail SMTP by WPForms.
<h4>Supported Languages</h4>
Although there are over 7000 languages spoken in the world today, we feel very lucky to support 30 languages for now.
However, localizing or adapting a plugin to another language or culture is time consuming and a demanding task. That’s where the amazing Translation Contributors team of WordPress comes into play. These selfless people spent their precious time without expecting anything in return so that other people can use the add-ons more easily. We sincerely thank all of them.
Chinese Simplified (China), Chinese Traditional (Taiwan), Czech, Dutch (Belgium), Dutch (Netherlands), English (South Africa), English (UK), Finnish, French (France), Galician, German (Germany), Hungarian, Indonesian, Italian, Japanese, Korean (Korea), Persian, Russian, Slovak (Slovakia), Slovenian, Spanish (Argentina), Spanish (Chile), Spanish (Colombia), Spanish (Ecuador), Spanish (Mexico), Spanish (Spain), Spanish (Venezuela), Swedish, Turkish, Ukrainian

WP Fastest Cache – WordPress Cache Plugin


The truth is that it is a pity that despite being a very good cache plugin, it only works for websites with one language.Confirmed with support that it does not pre-cache alternative urls to the native language of the website.


good plugin but... No languages?


I have tried so many different caching/optimization plugins and while others are bringing the page loading speed down to max 2.5-3 seconds WP Fastest Cache has really brought my website to 1.5 seconds loading time, this plugin is really the fastest caching plugin available it is incredibly good!


Really the fastest caching plugin (I've tried them all)


this is our favorite plugin for speeding up wordpress websites. works out of the box. 



we are also premium-users and it is worth the money!


great performance, great support


The support team is not only charming but also exceptionally helpful.


Amazing Support Team: Friendly and Helpful


Thank you so much for the amazing plugin you built, it works great with many project types!


Amazing Plugin

Prompt support


WP Fastest Cache works great on cloudways hosting, with support of varnish cache, it is even better than the recommended cache plugin created by cloudways.


Great plugin


It would be better if this plugin had some default settings not to cache EVERYTHING. Like doesn't matter if you have some important parameters in URL because it's the search results page - it will be cached and broken by default. 


Probably worst cache plugin you can choose

La mejor que he probado


I really enjoy using this wp-fastest-cache plugin. It is super easy to use and really helpful in speeding up the site.


Really love it.


I'm really impressed with their customer support, will highly recommend it!


Great Support and Quick Responses


WP Fastest Cache is solid for boosting site speed! Love the mod_rewrite approach and auto-cache clearing when you publish posts. CDN integration with Cloudflare/Bunny is smooth, plus the preload feature is handy. BUT heads up - it can mess with analytics by caching AJAX/JS requests. You can add filter rules but they don't always work perfectly. Great for speed, just watch your stats!


Speed Demon with a Few Quirks


Just installed and set some settings and runs like smooth. It actually works, If you know how, you'll be up/running in no time. This is a great plugin!


It works out of the box


As a developer, I appreciate plugins that deliver performance without bloat—and WP Fastest Cache nails it. It’s lightweight, easy to configure, and significantly boosts page load times out of the box. The minification, GZIP, and browser caching features just work as they should. If you need reliable caching without the overhead, this is your go-to.


Solid, Lightweight Caching That Just Works


I really like how easy it's to setup and it works great on Apache, NGINX and OLS. When I had an issue with a license, support was fast and great and I recovered access to the license without any problem.


Great Plugin and Support

Kevin Burkholder

The {eac}ObjectCache is a light-weight and very efficient drop-in persistent object cache that uses a fast SQLite database and even faster APCu shared memory to cache WordPress objects.
See <a href="https://developer.wordpress.org/reference/classes/wp_object_cache/" rel="nofollow ugc">The WordPress Object Cache</a>
<blockquote>
The WordPress Object Cache is used to save on trips to the database. The Object Cache stores all of the cache data to memory and makes the cache contents available by using a key, which is used to name and later retrieve the cache contents.
By default, the object cache is non-persistent. This means that data stored in the cache resides in memory only and only for the duration of the request. Cached data will not be stored persistently across page loads unless you install a persistent caching plugin.
</blockquote>
Here, an object is any piece of data – a number, text, a set of database records, an API response, etc. – that can be referenced by a name or key. Objects are categorized by a group name. Groups help identify what an object is and how it is used.
{eac}ObjectCache replaces the default WordPress object cache to not only store data in process memory but to also store data persistently, across requests, in APCu shared memory and/or in a SQLite database, increasing the likelihood of cache hits and decreasing the need for costly computations, complex MySQL database queries, and remote API requests.
SQLite is a fast, small, single-file relational database engine. By using SQLite to store objects, {eac}ObjectCache is able to manage a relatively large amount of data (groups, keys, and values) in a very efficient and fast data-store.
<a href="https://www.php.net/manual/en/book.apcu.php" rel="nofollow ugc">APCu</a> is a shared, in-memory, persistent cache available only when the <a href="https://www.php.net/manual/en/apcu.setup.php" rel="nofollow ugc">APCu PECL Extension</a> is installed. {eac}ObjectCache uses APCu as an intermediate cache between the L1 memory cache and the L2 SQLite database cache providing extremely fast object retrieval,
{eac}ObjectCache always uses per-request, in-memory caching and may operate with either APCu memory caching or SQLite database caching – or both. APCu memory caching uses a single block of memory shared by all PHP requests and is persistent until and unless the cache is cleared or the server is rebooted (or PHP restarted). SQLite database caching is persistent until and unless the cache is deliberately cleared.
<h4>Features</h4>
<ul>
<li>Lightweight, efficient, and fast!</li>
<li>L1 (in-process memory) and L2 (APCu & SQLite) caching.</li>
<li>Supports Write-Back (delayed transactions) or Write-Through SQL caching.</li>
<li>Caching by object group name.
<ul>
<li>Preserves uniqueness of keys.</li>
<li>Manage keys by group name.</li>
<li>Supports group name attributes (:sitewide, :nocaching, :permanent, :prefetch)</li>
</ul>
</li>
<li>Pre-fetch object groups from L2 to L1 cache.</li>
<li>Caches and pre-fetches L2 misses (known to not exist in L2 cache).
<ul>
<li>Prevents repeated, unnecessary L2 cache reads across requests.</li>
</ul>
</li>
<li>Multisite / Network support:
<ul>
<li>Cache/flush/switch by blog id.</li>
</ul>
</li>
<li>Caching statistics:
<ul>
<li>Cache hits (typically above 90%).</li>
<li>Overall and L1/L2 hits, misses, & ratio.</li>
<li>Cache hits by object groups.</li>
<li>Number of APCu and SQLite keys stored.</li>
<li>SQLite select/update/delete/commit counts.</li>
</ul>
</li>
<li>Supports an enhanced superset of WP Object Cache functions.</li>
<li>Easily enabled or disabled from {eac}Doojigger administrator page.
<ul>
<li>Imports existing MySQL transients.</li>
<li>Exports cached transients to MySQL when disabled.</li>
</ul>
</li>
<li>Automatically cleans and optimizes SQLite database.</li>
<li>Optionally schedule periodic cache invalidation and rebuild.</li>
<li>Uses the PHP Data Objects (PDO) extension included with PHP.</li>
</ul>
While {eac}ObjectCache does support multiple WordPress installations on a single server it does not support multiple servers per installation. SQLite and APCu work only on a single server, not in a clustered or load-balanced environment.
<h4>Configuration Alternatives</h4>
Assuming you have SQLite and APCu installed, what are your best options?
<ol>
<li>
Fastest Caching – Uses in-process memory and APCu shared memory.
<ul>
<li>Disable SQLite. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_USE_DB', false );</code></li>
</ul>
</li>
<li>Advantage
<ul>
<li>Fast memory-only access.</li>
<li>Handles concurrent updates through APCu cache.</li>
</ul>
</li>
<li>Disadvantage
<ul>
<li>APCu may invalidate data under memory constraint.</li>
<li>APCu cache is not shared with CLI.</li>
<li>APCu cache is lost on system or PHP restart.</li>
</ul>
</li>
</ul>
</li>
<li>
Less memory (almost as fast) – Uses in-process memory and APCu shared memory.
<ul>
<li>Disable SQLite. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_USE_DB', false );</code></li>
</ul>
</li>
<li>Optimize memory use. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );</code></li>
</ul>
</li>
<li>Advantage
<ul>
<li>Fast memory-only access.</li>
<li>Handles concurrent updates through APCu cache.</li>
<li>Conserves per-request memory by not pushing APCu hits to in-process memory.</li>
</ul>
</li>
<li>Disadvantage
<ul>
<li>Slightly slower to access APCu memory over in-process memory.</li>
<li>APCu may invalidate data under memory constraint.</li>
<li>APCu cache is not shared with CLI.</li>
<li>APCu cache is lost on system or PHP restart.</li>
</ul>
</li>
</ul>
</li>
<li>
Most resilient (and still fast) – Uses in-process memory, APCu shared memory, and SQLite database.
<ul>
<li>Do nothing, this is the default.</li>
<li>Advantage
<ul>
<li>Most cache hits will come from in-process and APCu memory.</li>
<li>SQLite retains cache data after restart.</li>
</ul>
</li>
<li>Disadvantage
<ul>
<li>Must keep SQLite database (on disk) updated.</li>
<li>Potential concurrency issues on high-volume site.</li>
</ul>
</li>
</ul>
</li>
<li>
Resilient, efficient, and fast (recommended) – Uses in-process memory, APCu shared memory, and SQLite database.
<ul>
<li>Optimize memory use. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );</code></li>
</ul>
</li>
<li>Advantage
<ul>
<li>Most cache hits will come from in-process and APCu memory.</li>
<li>Handles concurrent updates better through APCu cache.</li>
<li>Conserves per-request memory by not pushing APCu hits to in-process memory.</li>
<li>SQLite retains cache data after restart.</li>
</ul>
</li>
<li>Disadvantage
<ul>
<li>Slightly slower to access APCu memory over in-process memory.</li>
<li>Must keep SQLite database (on disk) updated.</li>
</ul>
</li>
</ul>
</li>
<li>
Least efficient (default when APCu is not installed) – Uses in-process memory and SQLite database.
<ul>
<li>Disable APCu. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_USE_APCU', false );</code></li>
</ul>
</li>
<li>Advantage
<ul>
<li>Saves resources by not taking up APCu reserves.</li>
<li>More secure by not using shared memory.</li>
<li>SQLite retains cache data after restart.</li>
</ul>
</li>
<li>Disadvantage
<ul>
<li>All cached data initially read from disk.</li>
<li>Must keep SQLite database (on disk) updated.</li>
<li>Potential concurrency issues on high-volume site.</li>
</ul>
</li>
</ul>
</li>
<li>
For high-volume sites – reduces or eliminates potential race conditions
<ul>
<li>Optimize memory use. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );</code></li>
</ul>
</li>
<li>Disable delayed writes. *
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_DELAYED_WRITES', false );</code></li>
</ul>
</li>
<li>Disable use of <code>alloptions</code> array.
<ul>
<li><code>define( 'EAC_OBJECT_CACHE_DISABLE_ALLOPTIONS', true );</code></li>
</ul>
</li>
<li>Advantage
<ul>
<li>Most cache hits will come from in-process and APCu memory.</li>
<li>Conserves per-request memory by not pushing APCu hits to in-process memory.</li>
<li>Updates SQLite data immediately.</li>
<li>Conserves per-request memory by elimination large <code>alloptions</code> array(s).</li>
</ul>
</li>
<li>Disadvantage
<ul>
<li>Slightly slower to access APCu memory over in-process memory.</li>
<li>Multiple single-row SQLite update transactions.</li>
<li>Slightly slower to access individual options from cache rather than <code>alloptions</code> array.</li>
</ul>
</li>
</ul>
</li>
</ol>
* These options may be set from the {eac}Doojigger administration screen.
When using SQLite, <code>delayed writes</code> (see below) dramatically improves efficiency by only writing updates at the end of the script process.
When using APCu shared memory, data is accessable by other PHP processes that may run on the server.
<h4>Inside The Numbers</h4>

 Label         
 Value
 cache hits 
 The total number of requests that returned a cached value.
 cache misses 
 The total number of requests that did not return a cached value. This number includes L1 cache (-), L2 non-persistent, L2 APCu (-), and L2 SQL misses.
 L1 cache hits 
 The number of requests that were found in the L1 memory cache.
 L1 cache (+) 
 Request found in the L1 memory cache with data (positive hits).
 L1 cache (-) 
 Request found in the L1 memory cache with no data (negative hits).
 L1 cache misses 
 The number of requests not found in the L1 memory cache.
 L2 non-persistent 
 L1 cache misses in a non-persistent group (not in L2 cache).
 L2 APCu hits 
 The number of L1 cache misses (minus L2 non-persistent) that were found in the L2 APCu cache.
 L2 APCu (+) 
 Request found in the L2 APCu cache with data (positive hits).
 L2 APCu (-) 
 Request found in the L2 APCu cache with no data (negative hits).
 L2 APCu misses 
 The number of requests not found in the L2 APCu cache.
 L2 SQL hits 
 The number of L2 APCu misses (or L1 cache misses) that were found in the L2 SQLite cache.
 L2 SQL misses 
 The number of requests not found in the L2 SQLite cache.
 L2 APCu updates 
 The number of APCu keys updated.
 L2 APCu deletes 
 The number of APCu keys deleted.
 L2 SQL selects 
 The number of SQLite select statements executed.
 L2 SQL updates 
 The number of SQLite records updated.
 L2 SQL deletes 
 The number of SQLite records deleted.
 L2 SQL commits 
 The number of SQLite transactions executed to update and delete records.
<ul>
<li>When a request results in a L2 SQL miss, the key is added to the L1 memory or L2 APCu cache as a miss so that additional requests for the same key do not result in additional SQL selects. This is known as a negative hit and still counted as a cache miss making the cache hit ratio (93.10%) understated.</li>
</ul>
Object cache statistics may be found:
<ul>
<li>In the WP Object Cache dashboard panel.
<ul>
<li>Uses <code>$wp_object_cache->showDashboardStats()</code></li>
</ul>
</li>
<li>In the Debug Bar > Object Cache panel.
<ul>
<li>Uses <code>$wp_object_cache->stats()</code></li>
</ul>
</li>
<li>In the Query Monitor > Logs > Info panel.
<ul>
<li>Uses <code>$wp_object_cache->getCurrentStats()</code></li>
</ul>
</li>
<li>In a wp_admin_notice block when display_stats is set for sampling.
<ul>
<li>Uses <code>$wp_object_cache->htmlStats()</code></li>
</ul>
</li>
</ul>
<h3>Settings</h3>
Several cache settings can be modified by adding defined constants to the <code>wp-config.php</code> file. The default settings are recommended and optimal in most cases but individual settings may need to be adjusted based on traffic volume, specific requirements, or unique circumstances. Most of these settings can be adjusted in the {eac}Doojigger administrator screen.
<ul>
<li>
To disable use of the SQLite Database (default: true):
<code>define( 'EAC_OBJECT_CACHE_USE_DB', false );</code>
</li>
</ul>
{eac}ObjectCache will still operate as an in-memory cache without the persistent database. If using APCu memory caching, persistence is maintained as long as the cache is not flushed, manually or by restarting PHP.
<ul>
<li>
To disable use of the APCu memory cache (default: true if APCu is enabled):
<code>define( 'EAC_OBJECT_CACHE_USE_APCU', false );</code>
</li>
</ul>
APCu memory caching is used, by default, only if the <a href="https://www.php.net/manual/en/apcu.installation.php" rel="nofollow ugc">APCu PECL extension</a> is installed.
<ul>
<li>
To optimize memory use when using APCu (default: false):
<code>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );</code>
</li>
</ul>
When using APCu memory caching, optimize internal memory by not storing APCu data in the L1 memory cache. This may slightly (negligibly) increase processing time as cache hits will come through APCu but will reduce the per-process memory usage. This may also be advantageous on high-volume sites where a single object may be updated by simultaneous processes.
<ul>
<li>
To disable use of the <code>alloptions</code> array in WordPress (default: false):
<code>define( 'EAC_OBJECT_CACHE_DISABLE_ALLOPTIONS', true );</code>
</li>
</ul>
By default, WordPress pre-fetches many of the option values from the wp-options table on startup. This facilitates faster access to oft-used options. However, this also creates 1) a potential race condition on high-volume sites, and 2) a sometimes very large array of data in memory that may also be duplicated in the L1 and L2 caches. Disabling this forces WordPress to get individual options from the cache rather than from the array, eliminates the race condition, eliminates the large array(s), and reduces much of the logic used to maintain the array(s). This may be particularly advantageous when using APCu since the option values should already be in shared memory.
* Once enabled, the caches should be cleared to eliminate previously cached <code>alloptions</code> arrays. 
* Uses filters <code>pre_wp_load_alloptions</code> (introduced in WP 6.2.0) and <code>wp_autoload_values_to_autoload</code> (introduced in WP 6.6.0).
<ul>
<li>
To set the location of the SQLite database (default: ../wp-content/cache):
<code>define( 'EAC_OBJECT_CACHE_DIR', '/full/path/to/folder' );</code>
</li>
</ul>
This folder can be outside of the web-accessable folders of your site – i.e. above the document root (htdocs, www, etc.) – provided that PHP can access (read/write) the folder (see the PHP open_basedir directive).
This folder should not be on a network share or other remote media. We’re caching data for quick access, the cache folder should be on fast, local media.
<ul>
<li>
To set the name of the SQLite database (default: ‘.eac_object_cache.sqlite’):
<code>define( 'EAC_OBJECT_CACHE_FILE', 'filename.sqlite' );</code>
</li>
</ul>
In addition to the database file, SQLite may also create temporary files using the same file name with a ‘-shm’ and ‘-wal’ suffix.
<ul>
<li>
To set SQLite journal mode (default: ‘WAL’):
<code>define( 'EAC_OBJECT_CACHE_JOURNAL_MODE', journal_mode )</code>
</li>
</ul>
journal_mode can be one of ‘DELETE’, ‘TRUNCATE’, ‘PERSIST’, ‘MEMORY’, ‘WAL’, or ‘OFF’. 
See <a href="https://www.sqlite.org/pragma.html#pragma_journal_mode" rel="nofollow ugc">SQLite journal mode</a>
<ul>
<li>
To set SQLite Mapped Memory I/O (default: 0):
<code>define( 'EAC_OBJECT_CACHE_MMAP_SIZE', int );</code>
</li>
</ul>
Sets the maximum number of bytes that are set aside for memory-mapped I/O. 
See <a href="https://www.sqlite.org/pragma.html#pragma_mmap_size" rel="nofollow ugc">SQLite memory-mapped I/O</a>
<ul>
<li>
To set SQLite Page Size (default: 4096):
<code>define( 'EAC_OBJECT_CACHE_PAGE_SIZE', int );</code>
</li>
</ul>
Sets the SQLite page size for the database. 
See <a href="https://www.sqlite.org/pragma.html#pragma_page_size" rel="nofollow ugc">SQLite page size</a>
<ul>
<li>
To set SQLite Cache Size (default: -2000 [2,048,000]):
<code>define( 'EAC_OBJECT_CACHE_CACHE_SIZE', int );</code>
</li>
</ul>
Sets the maximum number of database disk pages that SQLite will hold in memory or the maximum amount of memory to use for page caching. 
See <a href="https://www.sqlite.org/pragma.html#pragma_cache_size" rel="nofollow ugc">SQLite cache size</a>
<ul>
<li>
To set SQLite timeout (default: 3):
<code>define( 'EAC_OBJECT_CACHE_TIMEOUT', int );</code>
</li>
</ul>
Sets the number of seconds before a SQLite transaction may timeout in error.
<ul>
<li>
To set SQLite retries (default: 3):
<code>define( 'EAC_OBJECT_CACHE_MAX_RETRIES', int );</code>
</li>
</ul>
Sets the maximum number of retries to attempt on critical actions.
<ul>
<li>
To set delayed writes (default: 32):
<code>define( 'EAC_OBJECT_CACHE_DELAYED_WRITES', true|false|int );</code>
</li>
</ul>
{eac}ObjectCache caches all objects in memory and writes new, updated, or deleted objects to the L2 (SQLite) cache. delayed writes simply holds objects in memory until the number of objects reaches a specified threshold, then writes them, in a single transaction, to the L2 cache (a.k.a. write-back caching). Setting delayed writes to false turns this functionality off (a.k.a. write-through caching). Setting to true writes all records only at the end of the script process/page request. Setting this to a number sets the object pending threshold to that number of objects.
<ul>
<li>
To set the default expiration time (in seconds) (default: 0 [never]):
<code>define( 'EAC_OBJECT_CACHE_DEFAULT_EXPIRE', -1|0|int );</code>
</li>
</ul>
When using the default WordPress object cache, object expiration isn’t very important because the entire cache expires at the end of the script process/page request. With a persistent cache, this isn’t the case. When an object is cached, the developer has the option of specifying an expiration time for that object. Since we don’t know …

{eac}ObjectCache – a persistent object cache using SQLite & APCu to cache WordPress objects.

{eac}ObjectCache is a persistent object cache using APCu & SQLite to cache WordPress objects; A drop-in replacement to the WP Object Cache used by …

WP Fastest Cache – WordPress Cache Plugin vs {eac}ObjectCache – a persistent object cache using SQLite & APCu to cache WordPress objects.