by laruence 5 (1 reviews)

Yac Object Cache

Name: Yac Object Cache
Rating: 5.0 (1 reviews)
Author: laruence

Yac (lock-free shared memory) backed object cache for WordPress. Zero external servers, zero network round trips.

Yac Object Cache ranks #45,913 among WordPress.org plugins with 10+ active installations, is #671 of 1,658 in the Performance category, a 5/5 rating from 1 reviews, and was last updated Oct 19, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.4.1 Current Version v1.4.1

Updated 2 weeks ago Last Update on 19 Oct, 2026

Refreshed 1 week ago Last Refreshed on

#671 of 1,658 in Performance Top 50% by installs Actively maintained

View on WordPress.org

Rank

#45,913

— No change

Active Installs

10+

-44.4%

KW Avg Position

19.7

0.7 worse

Downloads

449

+1 today

Support Resolved

100%

— No change

Rating

100%

Review 5 out of 5

5 (1 reviews)

Next Milestone 20

Total Progress 50%

10+ 20+

22,740

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 5 more installs to reach 20+

Rank Changes

Current #45,913

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

1 reviews

Overall 100%

1 (100%)

0 (0%)

Support Threads Overview

Resolved

Unresolved

Total Threads

Resolved

Unresolved

100%

Resolution Rate

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.4.1
Last Updated: Oct 19, 2026
Requires WP: 5.6+
Tested Up To: 7.1.4
PHP Version: 7.0 or higher
Author: laruence

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 1
Support Threads: 2
Resolved: 100%

Keywords

cache object cache performance shared memory yac

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Wordfence Security – Firewall, Malware Scan, and Login Security

Speed Optimizer – The All-In-One Performance-Boosting Plugin

1M+ installs

#44

WP Fastest Cache – WordPress Cache Plugin

1M+ installs

#47

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

View all Performance plugins

Frequently Asked Questions

Common questions about Yac Object Cache

No. That is the point — the cache lives in shared memory on the machine.

The drop-in degrades to a per-request cache: the site keeps working, you lose cross-request persistence, and the status page flags the missing extension.

As <YAC_OCACHE_KEY_PREFIX>:<group>:<key> (default prefix wp), verbatim while they fit the 48-byte budget; over-long keys keep the group verbatim and hash (crc32b) only the key part.

Yes. wp_cache_flush() calls Yac::flush(), which wipes the entire shared memory on the machine, including data written by other Yac users sharing the PHP pool. The admin page asks for confirmation first.

Yes. On multisite the Yac instance prefix is YAC_OCACHE_KEY_PREFIX + the current blog id (ids up to 9999 verbatim, larger ids a 4-hex crc32b digest), and switch_to_blog() re-namespaces: blogs of one install get separate namespaces and never read each other's entries. The admin page follows the same split — the cache-status totals stay machine-wide, but the shared-memory contents, the group pie and the entry inspector are scoped to (and titled with) the blog you are viewing, so one blog never lists or edits another's entries. Installs sharing one PHP pool still need different YAC_OCACHE_KEY_PREFIX values.

Yac cannot delete entries by prefix, so a group flush clears the request-level copy of that group; shared entries then expire via TTL. The plugin reports flush_group as unsupported so core does not rely on it.