[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fq9ldLRSXT6xaWCGSSlqEyp3hMrHytRHHAzUBfK_ElQ8":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":38,"analysis":127,"fingerprints":230},"eacobjectcache","{eac}ObjectCache – a persistent object cache using SQLite & APCu to cache WordPress objects.","2.1.2","Kevin Burkholder","https:\u002F\u002Fprofiles.wordpress.org\u002Fkevinburkholder\u002F","\u003Cp>The \u003Cem>{eac}ObjectCache\u003C\u002Fem> 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.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Fclasses\u002Fwp_object_cache\u002F\" rel=\"nofollow ugc\">The WordPress Object Cache\u003C\u002Fa>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>{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\u002For 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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.apcu.php\" rel=\"nofollow ugc\">APCu\u003C\u002Fa> is a shared, in-memory, persistent cache available only when the \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fapcu.setup.php\" rel=\"nofollow ugc\">APCu PECL Extension\u003C\u002Fa> 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,\u003C\u002Fp>\n\u003Cp>{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.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Lightweight, efficient, and fast!\u003C\u002Fli>\n\u003Cli>L1 (in-process memory) \u003Cem>and\u003C\u002Fem> L2 (APCu & SQLite) caching.\u003C\u002Fli>\n\u003Cli>Supports Write-Back (delayed transactions) or Write-Through SQL caching.\u003C\u002Fli>\n\u003Cli>Caching by object group name.\n\u003Cul>\n\u003Cli>Preserves uniqueness of keys.\u003C\u002Fli>\n\u003Cli>Manage keys by group name.\u003C\u002Fli>\n\u003Cli>Supports group name attributes (:sitewide, :nocaching, :permanent, :prefetch)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Pre-fetch object groups from L2 to L1 cache.\u003C\u002Fli>\n\u003Cli>Caches and pre-fetches L2 misses (known to not exist in L2 cache).\n\u003Cul>\n\u003Cli>Prevents repeated, unnecessary L2 cache reads across requests.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Multisite \u002F Network support:\n\u003Cul>\n\u003Cli>Cache\u002Fflush\u002Fswitch by blog id.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Caching statistics:\n\u003Cul>\n\u003Cli>Cache hits (typically above 90%).\u003C\u002Fli>\n\u003Cli>Overall and L1\u002FL2 hits, misses, & ratio.\u003C\u002Fli>\n\u003Cli>Cache hits by object groups.\u003C\u002Fli>\n\u003Cli>Number of APCu and SQLite keys stored.\u003C\u002Fli>\n\u003Cli>SQLite select\u002Fupdate\u002Fdelete\u002Fcommit counts.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Supports an enhanced superset of WP Object Cache functions.\u003C\u002Fli>\n\u003Cli>Easily enabled or disabled from {eac}Doojigger administrator page.\n\u003Cul>\n\u003Cli>Imports existing MySQL transients.\u003C\u002Fli>\n\u003Cli>Exports cached transients to MySQL when disabled.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Automatically cleans and optimizes SQLite database.\u003C\u002Fli>\n\u003Cli>Optionally schedule periodic cache invalidation and rebuild.\u003C\u002Fli>\n\u003Cli>Uses the PHP Data Objects (PDO) extension included with PHP.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>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.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch4>Configuration Alternatives\u003C\u002Fh4>\n\u003Cp>Assuming you have SQLite and APCu installed, what are your best options?\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Fastest Caching – \u003Cem>Uses in-process memory and APCu shared memory.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable SQLite. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_USE_DB', false );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Advantage\n\u003Cul>\n\u003Cli>Fast memory-only access.\u003C\u002Fli>\n\u003Cli>Handles concurrent updates through APCu cache.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disadvantage\n\u003Cul>\n\u003Cli>APCu may invalidate data under memory constraint.\u003C\u002Fli>\n\u003Cli>APCu cache is not shared with CLI.\u003C\u002Fli>\n\u003Cli>APCu cache is lost on system or PHP restart.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Less memory (almost as fast) – \u003Cem>Uses in-process memory and APCu shared memory.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable SQLite. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_USE_DB', false );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Optimize memory use. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Advantage\n\u003Cul>\n\u003Cli>Fast memory-only access.\u003C\u002Fli>\n\u003Cli>Handles concurrent updates through APCu cache.\u003C\u002Fli>\n\u003Cli>Conserves per-request memory by not pushing APCu hits to in-process memory.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disadvantage\n\u003Cul>\n\u003Cli>Slightly slower to access APCu memory over in-process memory.\u003C\u002Fli>\n\u003Cli>APCu may invalidate data under memory constraint.\u003C\u002Fli>\n\u003Cli>APCu cache is not shared with CLI.\u003C\u002Fli>\n\u003Cli>APCu cache is lost on system or PHP restart.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Most resilient (and still fast) – \u003Cem>Uses in-process memory, APCu shared memory, and SQLite database.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Do nothing, this is the default.\u003C\u002Fli>\n\u003Cli>Advantage\n\u003Cul>\n\u003Cli>Most cache hits will come from in-process and APCu memory.\u003C\u002Fli>\n\u003Cli>SQLite retains cache data after restart.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disadvantage\n\u003Cul>\n\u003Cli>Must keep SQLite database (on disk) updated.\u003C\u002Fli>\n\u003Cli>Potential concurrency issues on high-volume site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Resilient, efficient, and fast (recommended) – \u003Cem>Uses in-process memory, APCu shared memory, and SQLite database.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Optimize memory use. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Advantage\n\u003Cul>\n\u003Cli>Most cache hits will come from in-process and APCu memory.\u003C\u002Fli>\n\u003Cli>Handles concurrent updates better through APCu cache.\u003C\u002Fli>\n\u003Cli>Conserves per-request memory by not pushing APCu hits to in-process memory.\u003C\u002Fli>\n\u003Cli>SQLite retains cache data after restart.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disadvantage\n\u003Cul>\n\u003Cli>Slightly slower to access APCu memory over in-process memory.\u003C\u002Fli>\n\u003Cli>Must keep SQLite database (on disk) updated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Least efficient (default when APCu is not installed) – \u003Cem>Uses in-process memory and SQLite database.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable APCu. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_USE_APCU', false );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Advantage\n\u003Cul>\n\u003Cli>Saves resources by not taking up APCu reserves.\u003C\u002Fli>\n\u003Cli>More secure by not using shared memory.\u003C\u002Fli>\n\u003Cli>SQLite retains cache data after restart.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disadvantage\n\u003Cul>\n\u003Cli>All cached data initially read from disk.\u003C\u002Fli>\n\u003Cli>Must keep SQLite database (on disk) updated.\u003C\u002Fli>\n\u003Cli>Potential concurrency issues on high-volume site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>For high-volume sites – \u003Cem>reduces or eliminates potential race conditions\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Optimize memory use. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disable delayed writes. *\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_DELAYED_WRITES', false );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disable use of \u003Ccode>alloptions\u003C\u002Fcode> array.\n\u003Cul>\n\u003Cli>\u003Ccode>define( 'EAC_OBJECT_CACHE_DISABLE_ALLOPTIONS', true );\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Advantage\n\u003Cul>\n\u003Cli>Most cache hits will come from in-process and APCu memory.\u003C\u002Fli>\n\u003Cli>Conserves per-request memory by not pushing APCu hits to in-process memory.\u003C\u002Fli>\n\u003Cli>Updates SQLite data immediately.\u003C\u002Fli>\n\u003Cli>Conserves per-request memory by elimination large \u003Ccode>alloptions\u003C\u002Fcode> array(s).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Disadvantage\n\u003Cul>\n\u003Cli>Slightly slower to access APCu memory over in-process memory.\u003C\u002Fli>\n\u003Cli>Multiple single-row SQLite update transactions.\u003C\u002Fli>\n\u003Cli>Slightly slower to access individual options from cache rather than \u003Ccode>alloptions\u003C\u002Fcode> array.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>* These options may be set from the {eac}Doojigger administration screen.\u003C\u002Fp>\n\u003Cp>\u003Cem>When using SQLite, \u003Ccode>delayed writes\u003C\u002Fcode> (see below) dramatically improves efficiency by only writing updates at the end of the script process.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>\u003Cem>When using APCu shared memory, data is accessable by other PHP processes that may run on the server.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch4>Inside The Numbers\u003C\u002Fh4>\n\u003C\u002Fp>\n\u003Cp>  Label        \u003Cbr \u002F>\n  Value\u003C\u002Fp>\n\u003Cp>  cache hits\u003Cbr \u002F>\n  The total number of requests that returned a cached value.\u003C\u002Fp>\n\u003Cp>  cache misses\u003Cbr \u002F>\n  The total number of requests that did not return a cached value. This number includes \u003Cem>L1 cache (-)\u003C\u002Fem>, \u003Cem>L2 non-persistent\u003C\u002Fem>, \u003Cem>L2 APCu (-)\u003C\u002Fem>, and \u003Cem>L2 SQL misses\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>  L1 cache hits\u003Cbr \u002F>\n  The number of requests that were found in the L1 memory cache.\u003C\u002Fp>\n\u003Cp>  L1 cache (+)\u003Cbr \u002F>\n  Request found in the L1 memory cache with data (positive hits).\u003C\u002Fp>\n\u003Cp>  L1 cache (-)\u003Cbr \u002F>\n  Request found in the L1 memory cache with no data (negative hits).\u003C\u002Fp>\n\u003Cp>  L1 cache misses\u003Cbr \u002F>\n  The number of requests not found in the L1 memory cache.\u003C\u002Fp>\n\u003Cp>  L2 non-persistent\u003Cbr \u002F>\n  L1 cache misses in a non-persistent group (not in L2 cache).\u003C\u002Fp>\n\u003Cp>  L2 APCu hits\u003Cbr \u002F>\n  The number of L1 cache misses (minus L2 non-persistent) that were found in the L2 APCu cache.\u003C\u002Fp>\n\u003Cp>  L2 APCu (+)\u003Cbr \u002F>\n  Request found in the L2 APCu cache with data (positive hits).\u003C\u002Fp>\n\u003Cp>  L2 APCu (-)\u003Cbr \u002F>\n  Request found in the L2 APCu cache with no data (negative hits).\u003C\u002Fp>\n\u003Cp>  L2 APCu misses\u003Cbr \u002F>\n  The number of requests not found in the L2 APCu cache.\u003C\u002Fp>\n\u003Cp>  L2 SQL hits\u003Cbr \u002F>\n  The number of L2 APCu misses (or L1 cache misses) that were found in the L2 SQLite cache.\u003C\u002Fp>\n\u003Cp>  L2 SQL misses\u003Cbr \u002F>\n  The number of requests not found in the L2 SQLite cache.\u003C\u002Fp>\n\u003Cp>  L2 APCu updates\u003Cbr \u002F>\n  The number of APCu keys updated.\u003C\u002Fp>\n\u003Cp>  L2 APCu deletes\u003Cbr \u002F>\n  The number of APCu keys deleted.\u003C\u002Fp>\n\u003Cp>  L2 SQL selects\u003Cbr \u002F>\n  The number of SQLite select statements executed.\u003C\u002Fp>\n\u003Cp>  L2 SQL updates\u003Cbr \u002F>\n  The number of SQLite records updated.\u003C\u002Fp>\n\u003Cp>  L2 SQL deletes\u003Cbr \u002F>\n  The number of SQLite records deleted.\u003C\u002Fp>\n\u003Cp>  L2 SQL commits\u003Cbr \u002F>\n  The number of SQLite transactions executed to update and delete records.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When a request results in a \u003Cem>L2 SQL miss\u003C\u002Fem>, 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 \u003Cem>negative hit\u003C\u002Fem> and still counted as a \u003Cem>cache miss\u003C\u002Fem> making the \u003Cem>cache hit ratio\u003C\u002Fem> (93.10%) understated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Object cache statistics may be found:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>In the \u003Cem>WP Object Cache\u003C\u002Fem> dashboard panel.\n\u003Cul>\n\u003Cli>Uses \u003Ccode>$wp_object_cache->showDashboardStats()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>In the \u003Cem>Debug Bar > Object Cache\u003C\u002Fem> panel.\n\u003Cul>\n\u003Cli>Uses \u003Ccode>$wp_object_cache->stats()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>In the \u003Cem>Query Monitor > Logs > Info\u003C\u002Fem> panel.\n\u003Cul>\n\u003Cli>Uses \u003Ccode>$wp_object_cache->getCurrentStats()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>In a \u003Cem>wp_admin_notice\u003C\u002Fem> block when \u003Cem>display_stats\u003C\u002Fem> is set for sampling.\n\u003Cul>\n\u003Cli>Uses \u003Ccode>$wp_object_cache->htmlStats()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Settings\u003C\u002Fh3>\n\u003Cp>Several cache settings can be modified by adding defined constants to the \u003Ccode>wp-config.php\u003C\u002Fcode> 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. \u003Cem>Most of these settings can be adjusted in the {eac}Doojigger administrator screen.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To disable use of the SQLite Database                       (default: true):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_USE_DB', false );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>{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.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To disable use of the APCu memory cache                     (default: true if APCu is enabled):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_USE_APCU', false );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>APCu memory caching is used, by default, only if the \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fapcu.installation.php\" rel=\"nofollow ugc\">APCu PECL extension\u003C\u002Fa> is installed.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To optimize memory use when using APCu                      (default: false):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_OPTIMIZE_MEMORY', true );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To disable use of the \u003Ccode>alloptions\u003C\u002Fcode> array in WordPress       (default: false):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_DISABLE_ALLOPTIONS', true );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>* \u003Cem>Once enabled, the caches should be cleared to eliminate previously cached \u003Ccode>alloptions\u003C\u002Fcode> arrays.\u003C\u002Fem>\u003Cbr \u002F>\n* \u003Cem>Uses filters \u003Ccode>pre_wp_load_alloptions\u003C\u002Fcode> (introduced in WP 6.2.0) and \u003Ccode>wp_autoload_values_to_autoload\u003C\u002Fcode> (introduced in WP 6.6.0).\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set the location of the SQLite database                  (default: ..\u002Fwp-content\u002Fcache):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_DIR', '\u002Ffull\u002Fpath\u002Fto\u002Ffolder' );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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\u002Fwrite) the folder (see the PHP \u003Cem>open_basedir\u003C\u002Fem> directive).\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set the name of the SQLite database                      (default: ‘.eac_object_cache.sqlite’):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_FILE', 'filename.sqlite' );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition to the database file, SQLite may also create temporary files using the same file name with a ‘-shm’ and ‘-wal’ suffix.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set SQLite journal mode                                  (default: ‘WAL’):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_JOURNAL_MODE', journal_mode )\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>journal_mode\u003C\u002Fem> can be one of ‘DELETE’, ‘TRUNCATE’, ‘PERSIST’, ‘MEMORY’, ‘WAL’, or ‘OFF’.\u003Cbr \u002F>\nSee \u003Ca href=\"https:\u002F\u002Fwww.sqlite.org\u002Fpragma.html#pragma_journal_mode\" rel=\"nofollow ugc\">SQLite journal mode\u003C\u002Fa>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set SQLite Mapped Memory I\u002FO                             (default: 0):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_MMAP_SIZE', int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Sets the maximum number of bytes that are set aside for memory-mapped I\u002FO.\u003Cbr \u002F>\nSee \u003Ca href=\"https:\u002F\u002Fwww.sqlite.org\u002Fpragma.html#pragma_mmap_size\" rel=\"nofollow ugc\">SQLite memory-mapped I\u002FO\u003C\u002Fa>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set SQLite Page Size                                     (default: 4096):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_PAGE_SIZE', int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Sets the SQLite page size for the database.\u003Cbr \u002F>\nSee \u003Ca href=\"https:\u002F\u002Fwww.sqlite.org\u002Fpragma.html#pragma_page_size\" rel=\"nofollow ugc\">SQLite page size\u003C\u002Fa>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set SQLite Cache Size                                    (default: -2000 [2,048,000]):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_CACHE_SIZE', int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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.\u003Cbr \u002F>\nSee \u003Ca href=\"https:\u002F\u002Fwww.sqlite.org\u002Fpragma.html#pragma_cache_size\" rel=\"nofollow ugc\">SQLite cache size\u003C\u002Fa>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set SQLite timeout                                       (default: 3):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_TIMEOUT', int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Sets the number of seconds before a SQLite transaction may timeout in error.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set SQLite retries                                       (default: 3):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_MAX_RETRIES', int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Sets the maximum number of retries to attempt on critical actions.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set delayed writes                                       (default: 32):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_DELAYED_WRITES', true|false|int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>{eac}ObjectCache caches all objects in memory and writes new, updated, or deleted objects to the L2 (SQLite) cache. \u003Cem>delayed writes\u003C\u002Fem> 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 \u003Cem>delayed writes\u003C\u002Fem> 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\u002Fpage request. Setting this to a number sets the object pending threshold to that number of objects.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>To set the default expiration time (in seconds)             (default: 0 [never]):\u003C\u002Fp>\n\u003Cp>\u003Ccode>define( 'EAC_OBJECT_CACHE_DEFAULT_EXPIRE', -1|0|int );\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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\u002Fpage 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  …\u003C\u002Fp>\n","{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 …",10,2383,100,2,"2025-10-25T13:38:00.000Z","6.8.5","5.8","8.1",[20,21,22,23,24],"apcu","object-cache","persistent-object-cache","sqlite","wp-cache","https:\u002F\u002Feacdoojigger.earthasylum.com\u002Feacobjectcache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feacobjectcache.2.1.2.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":13,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"kevinburkholder",6,60,30,94,"2026-04-03T23:15:48.248Z",[39,59,78,98,112],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":13,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":57,"download_link":58,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"sqlite-object-cache","SQLite Object Cache","1.6.1","OllieJones","https:\u002F\u002Fprofiles.wordpress.org\u002Folliejones\u002F","\u003Cp>A \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Fclasses\u002Fwp_object_cache\u002F#persistent-cache-plugins\" rel=\"nofollow ugc\">persistent object cache\u003C\u002Fa> helps your site perform well. This one uses the widely available \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.sqlite3.php\" rel=\"nofollow ugc\">SQLite3\u003C\u002Fa> extension, and optionally the \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fintro.igbinary.php\" rel=\"nofollow ugc\">igbinary\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.apcu.php\" rel=\"nofollow ugc\">APCu\u003C\u002Fa> extensions to php. Many hosting services offer those extensions, and they are easy to install on a server you control.\u003C\u002Fp>\n\u003Ch4>What is this about?\u003C\u002Fh4>\n\u003Cp>It’s about making your site’s web server perform better. An object cache does that by reducing the workload on your MariaDB or MySQL database. This is not a \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fadvanced-administration\u002Fperformance\u002Fcache\u002F\" rel=\"nofollow ugc\">page cache\u003C\u002Fa>; these persistent objects go into a different kind of cache. These objects aren’t chunks of web pages ready for people to view in their browsers, they are data objects for use by the WordPress software.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCache_(computing)\" rel=\"nofollow ugc\">Caches\u003C\u002Fa> are ubiquitous in computing, and WordPress has its own caching subsystem. Caches contain short-term copies of the results of expensive database lookups or computations, and allow software to use the copy rather than repeating the expensive operation. This plugin (like other object-caching plugins) extends WordPress’s caching subsystem to save those short-term copies from page view to page view. WordPress’s cache happens to be a \u003Ca href=\"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCache_(computing)#Memoization\" rel=\"nofollow ugc\">memoization\u003C\u002Fa> cache.\u003C\u002Fp>\n\u003Cp>Without a persistent object cache, every WordPress page view must use your MariaDB or MySQL database server to retrieve everything about your site. When a user requests a page, WordPress starts from scratch and loads everything it needs from your database server. Only then can it deliver content to your user. With a persistent object cache, WordPress immediately loads much of the information it needs. This lightens the load on your  database server and delivers content to your users faster.\u003C\u002Fp>\n\u003Ch4>Who should use this?\u003C\u002Fh4>\n\u003Cp>If your site runs on a single web server machine, and that server provides the \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.sqlite3.php\" rel=\"nofollow ugc\">SQLite3\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fintro.igbinary.php\" rel=\"nofollow ugc\">igbinary\u003C\u002Fa> extensions to php, this plugin will almost certainly make your site work faster. And if that server provides the \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.apcu.php\" rel=\"nofollow ugc\">APCu\u003C\u002Fa> extension, this plugin uses it too.\u003C\u002Fp>\n\u003Cp>Some hosting providers offer \u003Ca href=\"https:\u002F\u002Fredis.io\u002F\" rel=\"nofollow ugc\">redis\u003C\u002Fa> cache servers. If your provider offers redis, it may be a good choice. You can use it via the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fredis-cache\u002F\" rel=\"ugc\">Redis Object Cache\u003C\u002Fa> plugin. Sites using redis have one SQL database and another non-SQL storage server: redis. Other hosting providers offer \u003Ca href=\"https:\u002F\u002Fmemcached.org\u002F\" rel=\"nofollow ugc\">memcached\u003C\u002Fa>, which has the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmemcached\u002F\" rel=\"ugc\">Memcached Object Cache\u003C\u002Fa> plugin. And some large multipurpose cache plugins, such as the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flitespeed-cache\u002F\" rel=\"ugc\">LiteSpeed Cache\u003C\u002Fa>, also offer object caching based on one of those cache server software packages.\u003C\u002Fp>\n\u003Cp>The cache-server approach to object caching comes into its own when you have multiple load-balanced web server machines handling your site. SQLite doesn’t work correctly in a multiple-web-server environment.\u003C\u002Fp>\n\u003Cp>But, for single-server site configurations, SQLite, possibly assisted by APCu, performs well. And the vast majority of sites are single-server.\u003C\u002Fp>\n\u003Ch4>APCu\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.apcu.php\" rel=\"nofollow ugc\">APCu\u003C\u002Fa> is an in-memory storage medium. It lets php programs, like WordPress, store data in shared memory so it’s very fast to retrieve when needed. If APCu is available on your host server, you can configure this plugin to use it. It reduces the typical cache lookup time to one-fifth or less of the SQLite lookup time, which is itself a few tens of microseconds. Performance counts, especially on busy web sites.\u003C\u002Fp>\n\u003Cp>Please look at \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsqlite-object-cache\u002F#installation\" rel=\"ugc\">Installation\u003C\u002Fa> to learn how to configure this plugin to use APCu. The plugin works fast without it, and faster with it.\u003C\u002Fp>\n\u003Cp>WP-CLI: Even if APCu is in use, caching with SQLite is necessary when your web site uses WP-CLI, because WP-CLI programs do not have access to the APCu cache. This plugin writes all cached data both to APCu and to SQLite and makes sure the two are synchronized.\u003C\u002Fp>\n\u003Ch4>WP-CLI\u003C\u002Fh4>\n\u003Cp>You can control this plugin via WP-CLI once you activate it. Please type this command into your shell for details.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp help sqlite-object-cache\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Ftillkruess\u002F\" rel=\"nofollow ugc\">Till Krüss\u003C\u002Fa>. His \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fredis-cache\u002F\" rel=\"ugc\">Redis Object Cache\u003C\u002Fa> plugin serves as a model for this one. And thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Faristath\u002F\" rel=\"nofollow ugc\">Ari Stathopoulos\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fspacedmonkey\u002F\" rel=\"nofollow ugc\">Jonny Harris\u003C\u002Fa> for reviewing this. Props to Matt Jones for finding and fixing a bug that appeared on a heavily loaded system. Thanks to \u003Ca href=\"https:\u002F\u002Fspeedable.net\u002Fabout-us\u002F\" rel=\"nofollow ugc\">Massimo Villa\u003C\u002Fa> for testing help, and to \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnickchomey\" rel=\"nofollow ugc\">nickchomey\u003C\u002Fa> for a comprehensive code review. All defects are, of course, entirely the author’s responsibility.\u003C\u002Fp>\n\u003Cp>And thanks to Jetbrains for the use of their software development tools, especially \u003Ca href=\"https:\u002F\u002Fwww.jetbrains.com\u002Fphpstorm\u002F\" rel=\"nofollow ugc\">PhpStorm\u003C\u002Fa>. It’s hard to imagine how a plugin like this one could be developed without PhpStorm’s tools for exploring epic code bases like WordPress’s.\u003C\u002Fp>\n\u003Ch4>How can I learn more about making my WordPress site more efficient?\u003C\u002Fh4>\n\u003Cp>We offer several plugins to help with your site’s database efficiency. You can \u003Ca href=\"https:\u002F\u002Fwww.plumislandmedia.net\u002Fwordpress\u002Fperformance\u002Foptimizing-wordpress-database-servers\u002F\" rel=\"nofollow ugc\">read about them here\u003C\u002Fa>.\u003C\u002Fp>\n","A fast persistent object cache backend for the rest of us, powered by SQLite and accelerated by APCu",9000,100740,49,"2026-01-26T18:26:00.000Z","6.9.4","5.5","5.6",[20,55,21,56,23],"cache","performance","https:\u002F\u002Fgithub.com\u002FOllieJones\u002Fsqlite-object-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsqlite-object-cache.1.6.1.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":69,"num_ratings":70,"last_updated":71,"tested_up_to":51,"requires_at_least":72,"requires_php":18,"tags":73,"homepage":76,"download_link":77,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"apcu-manager","APCu Manager","4.3.0","Pierre Lannoy","https:\u002F\u002Fprofiles.wordpress.org\u002Fpierrelannoy\u002F","\u003Cp>\u003Cstrong>APCu statistics and management right in the WordPress admin dashboard.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> is a full featured APCu management and analytics reporting tool. It allows you to monitor and optimize APCu operations on your WordPress site or network.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> offers a persistent object cache backend to WordPress: just activate the option in the settings and you will experience a real speed up of your site or network.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> works on dedicated or shared servers. It is compatible with all plugins using APCu, like PerfOps One suite or W3 Total Cache. Its main management features are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>drop-in replacement for WordPress object caching;\u003C\u002Fli>\n\u003Cli>individual object deletion;\u003C\u002Fli>\n\u003Cli>bulk object deletion;\u003C\u002Fli>\n\u003Cli>objects browsing and inspecting;\u003C\u002Fli>\n\u003Cli>smart garbage collection;\u003C\u002Fli>\n\u003Cli>full cache clearing.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>⚠️ \u003Cstrong>APCu Manager\u003C\u002Fstrong> doesn’t work on PHP clustered environments!\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> is also a full featured analytics reporting tool that analyzes all APCu operations on your site. It can report:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>KPIs: hit ratio, free memory, cached objects, keys saturation, memory fragmentation and availability;\u003C\u002Fli>\n\u003Cli>metrics variations;\u003C\u002Fli>\n\u003Cli>metrics distributions;\u003C\u002Fli>\n\u003Cli>plugins consumption.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> supports multisite report delegation (see FAQ).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> supports a set of WP-CLI commands to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>toggle on\u002Foff main settings – see \u003Ccode>wp help apcu settings\u003C\u002Fcode> for details;\u003C\u002Fli>\n\u003Cli>obtain operational statistics – see \u003Ccode>wp help apcu analytics\u003C\u002Fcode> for details.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For a full help on WP-CLI commands in APCu Manager, please \u003Ca href=\"https:\u002F\u002Fperfops.one\u002Fapcu-manager-wpcli\" rel=\"nofollow ugc\">read this guide\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> is part of \u003Ca href=\"https:\u002F\u002Fperfops.one\u002F\" rel=\"nofollow ugc\">PerfOps One\u003C\u002Fa>, a suite of free and open source WordPress plugins dedicated to observability and operations performance.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>APCu Manager\u003C\u002Fstrong> is a free and open source plugin for WordPress. It integrates many other free and open source works (as-is or modified). Please, see ‘about’ tab in the plugin settings to see the details.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>This plugin is free and provided without warranty of any kind. Use it at your own risk, I’m not responsible for any improper use of this plugin, nor for any damage it might cause to your site. Always backup all your data before installing a new plugin.\u003C\u002Fp>\n\u003Cp>Anyway, I’ll be glad to help you if you encounter issues when using this plugin. Just use the support section of this plugin page.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin, as any piece of software, is neither compliant nor non-compliant with privacy laws and regulations. It is your responsibility to use it with respect for the personal data of your users and applicable laws.\u003C\u002Fp>\n\u003Cp>This plugin doesn’t set any cookie in the user’s browser.\u003C\u002Fp>\n\u003Cp>This plugin doesn’t handle personally identifiable information (PII).\u003C\u002Fp>\n\u003Ch4>Donation\u003C\u002Fh4>\n\u003Cp>If you like this plugin or find it useful and want to thank me for the work done, please consider making a donation to \u003Ca href=\"https:\u002F\u002Fwww.laquadrature.net\u002Fen\" rel=\"nofollow ugc\">La Quadrature Du Net\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fwww.eff.org\u002F\" rel=\"nofollow ugc\">Electronic Frontier Foundation\u003C\u002Fa> which are advocacy groups defending the rights and freedoms of citizens on the Internet. By supporting them, you help the daily actions they perform to defend our fundamental freedoms!\u003C\u002Fp>\n","APCu statistics and management right in the WordPress admin dashboard.",10000,131451,92,20,"2025-11-22T13:21:00.000Z","6.2",[20,55,74,21,75],"monitor","w3tc","https:\u002F\u002Fperfops.one\u002Fapcu-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fapcu-manager.4.3.0.zip",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":88,"num_ratings":89,"last_updated":90,"tested_up_to":51,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":96,"download_link":97,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"atec-cache-apcu","atec Cache APCu","2.3.68","docjojo","https:\u002F\u002Fprofiles.wordpress.org\u002Fdocjojo\u002F","\u003Cp>atec Cache APCu provides a drop-in object-cache and optional page cache, built entirely on APCu.\u003C\u002Fp>\n\u003Cp>It replaces WordPress’s core cache with a fast, persistent alternative — offering major performance gains, especially on single-server setups.\u003C\u002Fp>\n\u003Cp>APCu is faster than Redis and Memcached in low-latency scenarios. This plugin uses advanced logic that improves object cache efficiency by up to 16.67%.\u003C\u002Fp>\n\u003Cp>The optional page cache is the only APCu-powered full-page cache for WordPress, and includes cache exclusion rules, cache flushing and profiler\u002Fdebugging options.\u003C\u002Fp>\n\u003Ch3>Specifications\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Includes object cache drop-in and optional full page cache  \u003C\u002Fli>\n\u003Cli>Profiler and debug options for diagnostics\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>APCu extension enabled\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Third-Party Services\u003C\u002Fh3>\n\u003Ch3>Integrity check\u003C\u002Fh3>\n\u003Cp>Once, when activating the plugin, an integrity check is requested from our server – if you give your permission.\u003Cbr \u002F>\nSource: https:\u002F\u002Fatecplugins.com\u002F\u003Cbr \u002F>\nPrivacy policy: https:\u002F\u002Fatecplugins.com\u002Fprivacy-policy\u002F\u003C\u002Fp>\n\u003Ch3>‘PRO’ Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>AOC Mode (Advanced Object Cache)\u003Cbr \u002F>\nAdvanced Object Cache Mode – takes full advantage of APCu’s in-memory array support, eliminating unnecessary serialize()\u002Funserialize() cycles and boosting PHP performance on every request.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>APC Mode (Advanced Page Cache)\u003Cbr \u002F>\nAdvanced Page Cache is a ‘PRO’-level optimization that activates earlier than regular page cache — before most WordPress logic even runs.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","Super fast APCu-based Object Cache and the only APCu-powered Page Cache plugin for WordPress.",1000,84890,98,19,"2026-01-08T13:01:00.000Z","4.9","7.4",[20,21,94,56,95],"page-cache","persistent-cache","https:\u002F\u002Fatecplugins.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fatec-cache-apcu.2.3.68.zip",{"slug":99,"name":100,"version":101,"author":82,"author_profile":83,"description":102,"short_description":103,"active_installs":86,"downloaded":104,"rating":13,"num_ratings":105,"last_updated":106,"tested_up_to":51,"requires_at_least":91,"requires_php":92,"tags":107,"homepage":96,"download_link":111,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"atec-cache-info","atec Cache Info","1.8.31","\u003Cp>atec Cache Info gives you a complete overview of all system-level caching used by your WordPress installation.\u003C\u002Fp>\n\u003Cp>It detects and displays:\u003Cbr \u002F>\n* OPcache status\u003Cbr \u002F>\n* PHP JIT support\u003Cbr \u002F>\n* Object Cache type and health\u003Cbr \u002F>\n* APCu presence and statistics\u003Cbr \u002F>\n* Redis and Memcached availability\u003Cbr \u002F>\n* SQLite Object Cache support (if any)\u003C\u002Fp>\n\u003Cp>Use this plugin to diagnose performance bottlenecks, verify cache setup, and ensure that all critical caches are working correctly.\u003C\u002Fp>\n\u003Ch3>Specifications\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Compatible with: APCu, Memcached, Redis, SQLite\u003C\u002Fli>\n\u003Cli>Displays runtime statistics and limits\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Third-Party Services\u003C\u002Fh3>\n\u003Ch3>Integrity check\u003C\u002Fh3>\n\u003Cp>Once, when activating the plugin, an integrity check is requested from our server – if you give your permission.\u003Cbr \u002F>\nSource: https:\u002F\u002Fatecplugins.com\u002F\u003Cbr \u002F>\nPrivacy policy: https:\u002F\u002Fatecplugins.com\u002Fprivacy-policy\u002F\u003C\u002Fp>\n","Show system cache status and statistics for OPcache, JIT, Object Cache, APCu, Redis, Memcached, and SQLite Cache.",61810,9,"2025-12-18T09:31:00.000Z",[20,108,21,109,110],"memcached","opcache","redis","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fatec-cache-info.1.8.31.zip",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":13,"downloaded":120,"rating":27,"num_ratings":27,"last_updated":121,"tested_up_to":51,"requires_at_least":53,"requires_php":122,"tags":123,"homepage":125,"download_link":126,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"apcu-object-cache","Object Cache for APCu – ZapCu","1.0.0","wpdebuglog","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpdebuglog\u002F","\u003Cp>\u003Cstrong>Object Cache for APCu\u003C\u002Fstrong> enables persistent object caching in WordPress using the APCu extension. It helps reduce database queries by caching objects in memory, speeding up page loads and backend performance.\u003Cbr \u002F>\n\u003Cstrong>Requires: \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.apcu.php\" rel=\"nofollow ugc\">APCu extension\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> \u003Ca href=\"https:\u002F\u002Fwww.fastcomet.com\u002Fkb\u002Fenable-apcu-caching\" rel=\"nofollow ugc\">How to Enable APCu Caching (cPanel)\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>⚠️ Make sure APCu is enabled on your server before activating this plugin.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003Cbr \u002F>\n* Uses APCu for WordPress object caching.\u003Cbr \u002F>\n* Dashboard with real-time APCu stats (hits, misses, memory, inserts, etc.).\u003Cbr \u002F>\n* Clear\u002Freset cache with one click (protected by nonce).\u003Cbr \u002F>\n* Automatically installs \u003Ccode>object-cache.php\u003C\u002Fcode> in wp-content.\u003Cbr \u002F>\n* Clean, professional admin interface.\u003C\u002Fp>\n","Lightweight object caching plugin using PHP's APCu extension for fast in-memory caching and performance boost.",1320,"2026-01-30T03:50:00.000Z","7.2",[20,55,21,124,56],"optimization","https:\u002F\u002Fwpdebuglog.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fapcu-object-cache.1.0.0.zip",{"attackSurface":128,"codeSignals":178,"taintFlows":219,"riskAssessment":220,"analyzedAt":229},{"hooks":129,"ajaxHandlers":174,"restRoutes":175,"shortcodes":176,"cronEvents":177,"entryPointCount":27,"unprotectedCount":27},[130,136,141,146,150,153,157,162,164,168,171],{"type":131,"name":132,"callback":133,"file":134,"line":135},"action","admin_footer","closure","detached-install.php",46,{"type":137,"name":138,"callback":133,"file":139,"line":140},"filter","eacDoojigger_load_extensions","eacObjectCache.php",51,{"type":131,"name":142,"callback":143,"file":144,"line":145},"options_settings_page","admin_options_settings","Extensions\\class.eacObjectCache.admin.extension.php",65,{"type":131,"name":147,"callback":148,"file":144,"line":149},"options_settings_help","admin_options_help",67,{"type":131,"name":151,"callback":133,"file":144,"line":152},"options_form_post",502,{"type":131,"name":154,"callback":154,"file":155,"line":156},"rebuild_object_cache","Extensions\\class.eacObjectCache.extension.php",108,{"type":131,"name":158,"callback":159,"file":160,"line":161},"wp_cache_set_last_changed","cache_clear_query_groups","src\\object-cache.php",495,{"type":131,"name":132,"callback":133,"file":160,"line":163},505,{"type":131,"name":165,"callback":133,"priority":166,"file":160,"line":167},"shutdown",8,514,{"type":137,"name":169,"callback":133,"file":160,"line":170},"pre_wp_load_alloptions",572,{"type":137,"name":172,"callback":133,"file":160,"line":173},"wp_autoload_values_to_autoload",575,[],[],[],[],{"dangerousFunctions":179,"sqlUsage":180,"outputEscaping":186,"fileOperations":217,"externalRequests":27,"nonceChecks":27,"capabilityChecks":27,"bundledLibraries":218},[],{"prepared":33,"raw":181,"locations":182},1,[183],{"file":160,"line":184,"context":185},2987,"$wpdb->query() with variable interpolation",{"escaped":187,"rawEcho":188,"locations":189},18,13,[190,193,195,197,199,201,203,205,207,209,211,213,215],{"file":134,"line":191,"context":192},54,"raw output",{"file":134,"line":194,"context":192},61,{"file":160,"line":196,"context":192},2523,{"file":160,"line":198,"context":192},2664,{"file":160,"line":200,"context":192},2672,{"file":160,"line":202,"context":192},2684,{"file":160,"line":204,"context":192},2697,{"file":160,"line":206,"context":192},2709,{"file":160,"line":208,"context":192},2734,{"file":160,"line":210,"context":192},2764,{"file":160,"line":212,"context":192},2776,{"file":160,"line":214,"context":192},2793,{"file":160,"line":216,"context":192},2806,5,[],[],{"summary":221,"deductions":222},"Based on the static analysis, the eacobjectcache plugin version 2.1.2 appears to have a generally good security posture. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points is a significant strength, indicating a limited attack surface. The code signals also show a strong reliance on prepared statements for SQL queries, which is a best practice. However, there are areas for concern. The output escaping is only properly implemented in 58% of cases, suggesting a potential risk of cross-site scripting (XSS) vulnerabilities if user-supplied data is not handled carefully. The lack of nonce checks and capability checks across all identified entry points (though there are none) is noted, but the current lack of entry points mitigates this risk for now.  The vulnerability history being entirely clear is a positive indicator, suggesting that the plugin has not historically been a source of significant security flaws.  Overall, while the plugin benefits from a small attack surface and good SQL practices, the less-than-ideal output escaping warrants attention for any future development or updates.",[223,225,227],{"reason":224,"points":166},"Output escaping is not consistently implemented",{"reason":226,"points":217},"No nonce checks detected",{"reason":228,"points":217},"No capability checks detected","2026-03-17T00:01:43.161Z",{"wat":231,"direct":237},{"assetPaths":232,"generatorPatterns":234,"scriptPaths":235,"versionParams":236},[233],"\u002Fwp-content\u002Fplugins\u002Feacobjectcache\u002FeacObjectCache.php",[],[],[],{"cssClasses":238,"htmlComments":239,"htmlAttributes":246,"restEndpoints":259,"jsGlobals":260,"shortcodeOutput":262},[],[240,241,242,243,244,245],"\u003C!-- {eac}Doojigger Object Cache - SQLite and APCu powered WP_Object_Cache Drop-in -->","\u003C!-- Derived from WordPress core WP_Object_Cache (wp-includes\u002Fclass-wp-object-cache.php) -->","\u003C!-- {eac}ObjectCache is an extension plugin to and is fully functional with installation and registration of","{eac}Doojigger (see: https:\u002F\u002Feacdoojigger.earthasylum.com\u002F).","However, the core 'object-cache.php' file may be installed without {eac}Doojigger - referred to as 'detached' mode.","- - -",[247,248,249,250,251,252,253,254,255,256,257,258],"data-eac-object-cache-disabled","data-eac-object-cache-flush-action","data-eac-object-cache-flush-group","data-eac-object-cache-flush-nonce","data-eac-object-cache-flush-site","data-eac-object-cache-flush-type","data-eac-object-cache-flush-url","data-eac-object-cache-flush-wpnonce","data-eac-object-cache-stats-action","data-eac-object-cache-stats-nonce","data-eac-object-cache-stats-url","data-eac-object-cache-stats-wpnonce",[],[261],"eacObjectCacheAdmin",[]]