atec Cache APCu - ChoosePlugin.com

This plugin provides a simple but effective APCu object cache.

Author:	docjojo (profile at wordpress.org)
WordPress version required:	4.9
WordPress version tested:	6.9.4
Plugin version:	2.3.71
Added to WordPress repository:	14-06-2023
Last updated:	24-03-2026
Rating, %:	98
Rated by:	19
Plugin URI:	https://atecplugins.com/
Total downloads:	87 687
Active installs:	2 000+
Click to start download

atec Cache APCu provides a drop-in object-cache and optional page cache, built entirely on APCu.

It replaces WordPress’s core cache with a fast, persistent alternative — offering major performance gains, especially on single-server setups.

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%.

The optional page cache is the only APCu-powered full-page cache for WordPress, and includes cache exclusion rules, cache flushing and profiler/debugging options.

Specifications

Includes object cache drop-in and optional full page cache
Profiler and debug options for diagnostics

Requirements

APCu extension enabled

Third-Party Services

Integrity check

Once, when activating the plugin, an integrity check is requested from our server – if you give your permission.
Source: https://atecplugins.com/
Privacy policy: https://atecplugins.com/privacy-policy/

‘PRO’ Features

AOC Mode (Advanced Object Cache)
Advanced Object Cache Mode – takes full advantage of APCu’s in-memory array support, eliminating unnecessary serialize()/unserialize() cycles and boosting PHP performance on every request.
APC Mode (Advanced Page Cache)
Advanced Page Cache is a ‘PRO’-level optimization that activates earlier than regular page cache — before most WordPress logic even runs.

Screenshots
FAQ

– What is Object caching?
Object caching involves storing variables and database queries thereby speeding up PHP execution times. This reduces the load on your server, and delivers content to your visitors faster.

– What is Page caching?
Page caching refers to caching the content of a whole page on the server-side. Later when the same page is requested again, its content will be served from the cache instead of regenerating it from scratch.

Does the object-cache also work in WP-CLI?
If you use WP-CLI to run .php scripts, please set “apc.enable_cli=1” in your php.ini – otherwise object-cache will not work.
Is the page cache multisite compatibel?
This plugin isn’t optimized for multisite environments. Since multisite setups require incorporating a blog ID — a feature not supported by this plugin — we recommend using our “mega-cache” plugin instead.
Is the page cache multi-language compatibel?
This depends on the translation plugin being used. When translations are performed on the fly, the page or post ID remains unchanged, preventing “atec-cache-apcu” from detecting any differences. Please use our “mega-cache” plugin instead.

Does this work with WooCommerce?

Partly. Cart, checkout, and account pages are automatically excluded from the page cache.

Will this work on shared hosting?

Ye – if APCu is available. It is ideal for VPS or dedicated servers.

Can I use Redis or Memcached with this?

No. This plugin is APCu-only and does not require other memory caches.

What makes this faster than other solutions?

It uses pure APCu without network latency, with optimized logic for set/get/flush and auto-purging support.

How do I use DONOTCACHEPAGE to skip page caching for specific requests?

You can define the constant DONOTCACHEPAGE to prevent a page from being stored in the cache. To use it correctly, make sure it is defined early during WordPress execution — before output begins.

For example, in a plugin or theme:

add_action('template_redirect', function() {
    if ( is_page('thank-you') || is_user_logged_in() ) {
        define('DONOTCACHEPAGE', true);
    }
});

This ensures the current request is processed normally but not stored in the page cache.

Important:
If a page has already been cached, this logic will not run — because the cached version is served before WordPress reaches your code. To apply new exclusions like this, make sure to purge the page cache after defining the logic.

Hide FAQ

ChangeLog

Specifications

Requirements

Third-Party Services

Integrity check

‘PRO’ Features

2.3.71 [2026.03.23]

2.3.70 [2026.03.18]

2.3.69 [2026.01.21]

2.3.68 [2026.01.05]

2.3.67 [2026.01.02]

2.3.66 [2026.01.02]

2.3.65 [2026.01.02]

2.3.64 [2026.01.02]

2.3.63 [2026.01.02]

2.3.62 [2025.12.09]

2.3.61 [2025.12.06]

2.3.60 [2025.12.02]

2.3.59 [2025.12.02]

2.3.58 [2025.11.04]

2.3.57 [2025.11.04]

2.3.56 [2025.10.21]

2.3.55 [2025.10.12]

2.3.54 [2025.10.11]

2.3.53 [2025.09.27]

2.3.52 [2025.09.09]

2.3.51 [2025.08.10]

2.3.50 [2025.08.09]

2.3.44 [2025.08.09]

2.3.43 [2025.08.09]

2.3.42 [2025.08.09]

2.3.41 [2025.08.09]

2.3.40 [2025.08.09]

2.3.39 [2025.08.09]

2.3.38 [2025.08.06]

2.3.37 [2025.08.06]

2.3.36 [2025.08.06]

2.3.35 [2025.08.03]

2.3.34 [2025.07.30]

2.3.33 [2025.07.30]

2.3.32 [2025.07.30]

2.3.31 [2025.07.30]

2.3.30 [2025.07.23]

2.3.29 [2025.07.22]

2.3.28 [2025.07.22]

2.3.27 [2025.07.22]

2.3.26 [2025.07.22]

2.3.25 [2025.07.19]

2.3.24 [2025.07.08]

2.3.21 [2025.07.08]

2.3.20 [2025.07.03]

2.3.19 [2025.07.02]

2.3.18 [2025.06.28]

2.3.17 [2025.06.26]

2.3.16 [2025.06.26]

2.3.15 [2025.06.26]

2.3.14 [2025.06.26]

2.3.13 [2025.06.25]

2.3.12 [2025.06.25]

2.3.11 [2025.06.25]

2.3.10 [2025.06.25]

2.3.9 [2025.06.25]

2.3.8 [2025.06.24]

2.3.7 [2025.06.24]

2.3.5 [2025.06.19]

2.1.97 [2025.04.30]

2.1.95 [2025.04.23]

2.1.94 [2025.04.23]

2.1.93 [2025.04.06]

2.1.92 [2025.04.05]

2.1.91 [2025.04.03]

2.1.89 [2025.03.28]

2.1.88 [2025.03.28]

2.1.86 [2025.03.16]

2.1.85 [2025.03.14]

2.1.84 [2025.03.07]

2.1.83 [2025.03.07]

2.1.82 [2025.03.07]

2.1.81 [2025.03.07]

2.1.80 [2025.03.07]

2.1.79 [2025.03.04]