For sites concerned with high traffic, speed for logged-in users, or dynamic pageloads, a high-speed and persistent object cache is a must. WP LCache improves upon Memcached and Redis object cache implementations by using APCu, PHP’s in-memory cache, in a way that’s compatible with multiple web nodes. Under the hood, WP LCache uses LCache, a library that applies the tiered caching model of multi-core processors (with local L1 and central L2 caches) to web applications.
Note: WP LCache development is currently on hold, and not recommendated for production use, due to an issue with APCu cache fragmentation. WP Redis, also maintained by Pantheon, is a great alternative.
WP LCache is faster than other object cache implementations because:
- By using APCu, which is in-memory, WP LCache uses the fastest possible persistent object cache backend and avoids costly network connections on every request. When using a Memcached or Redis-based persistent object cache where Memcached or Redis is on a different machine, the millisecond cost of each cache hit can add up to seconds of network transactions on every request.
- By incorporating a common L2 cache, WP LCache synchronizes cache data between multiple web nodes. Cache updates or deletes on one node are then applied to all other nodes. Without this synchronization behavior, APCu can’t be used in server configurations with multiple web nodes because the cache pool is local to the machine.
Still not convinced? WP LCache includes features that no one else has:
- Cache groups are handled natively, meaning you can delete an entire group of keys with
- WordPress’ alloptions cache is sharded into distinct keys, mitigating cache pollution on high traffic sites. Read #31245 for all of the gory details.
Go forth and make awesome! And, once you’ve built something great, send us feature requests (or bug reports).
The best way to contribute to the development of this plugin is by participating on the GitHub project:
Pull requests and issues are welcome!
You may notice there are two sets of tests running, on two different services:
- Travis CI runs the PHPUnit test suite in a variety of environment configurations (e.g. APCu available vs. APCu unavailable).
- Circle CI runs the Behat test suite against a Pantheon site, to ensure the plugin’s compatibility with the Pantheon platform.
Both of these test suites can be run locally, with a varying amount of setup.
PHPUnit requires the WordPress PHPUnit test suite, and access to a database with name
wordpress_test. If you haven’t already configured the test suite locally, you can run
bash bin/install-wp-tests.sh wordpress_test root '' localhost. You’ll also need to install and configure APCu in order to run the test suite against APCu.
Behat requires a Pantheon site. Once you’ve created the site, you’ll need install Terminus, and set the
TERMINUS_ENV environment variables. Then, you can run
./bin/behat-prepare.sh to prepare the site for the test suite.
WP LCache requires PHP 5.6 or greater with the APCu extension enabled.
To install WP LCache, follow these steps:
- Install the plugin from WordPress.org using the WordPress dashboard.
1a. Those installing from Github will need to run
composer install --no-dev --no-scriptsafter cloning to get the LCache library.
- Activate the plugin, to ensure LCache’s database tables are created. These are created on the plugin activation hook.
- Create a stub file at
wp-content/object-cache.php file should contain:
<?php # Engage LCache object caching system. # We use a 'require_once()' here because in PHP 5.5+ changes to symlinks # are not detected by the opcode cache, making it frustrating to deploy. # # More info: http://codinghobo.com/opcache-and-symlink-based-deployments/ # $lcache_path = dirname( realpath( __FILE__ ) ) . '/plugins/wp-lcache/object-cache.php'; require_once( $lcache_path );
To install WP LCache in one line with WP-CLI:
wp plugin install wp-lcache --activate && wp lcache enable
If you need to install APCu, the PECL installer is the easiest way to do so.
- PHP 7.0:
pecl install apcu
- PHP 5.6:
pecl install channel://pecl.php.net/apcu-4.0.11
Enabling APCu for CLI is a matter of adding
apc.enable_cli='on' to your
If you can’t easily use PHP 5.6 or greater, you should switch to a more responsible hosting provider.
If any of the requirements for LCache to function are not met, you will see an admin notice indicating the issue. Here’s how to resolve issues for each possible dependency:
- “LCache database table”: This indicates you have the
object-cache.phpsymlink in place, but have not activated the plugin (which installs the LCache db table). Activate the plugin and verify the LCache tables are created.
- “PHP 5.6 or greater”: You need to update your PHP runtime, which will also make your site faster and more secure. Do it today, or contact your hosting provider if you don’t have access.
- “APCu extension installed/enabled”: You don’t have the required PHP extension to power LCache. See above instructions for installing APCU, or contact your hosting provider.
- “LCache library”: you’re probably installing direct from GitHub, not a download from the WordPress.org plugins directory. Awesome! You just need to run
composer install --no-devinside the
wp-lcachedirectory, and make sure the resulting
vendordirectory is deployed along with the rest of
- Do you have benchmarks you can share?
We’ve done some rudimentary testing with New Relic on Pantheon infrastructure. The results were substantial enough for us to begin using LCache in production. Watch David Strauss’ DrupalCon presentation for a more thorough explanation.
If you’d like to do some benchmarking yourself, we’d love to hear about your testing methodology and conclusions. Caching is more of an art than a science, and outcomes can vary. Because cost of network transactions is one of the problems solved by WP LCache, the performance gains will be more impressive if you’ve historically been using Redis or Memcached on a separate machine.
- Is APCu persistent like Redis is?
APCu is persistent through the life of a PHP-FPM process. However, unlike Redis, APCu doesn’t save its state to disk at shutdown. When PHP-FPM is restarted, WP LCache will repopulate the L1 cache (APCu) from the L2 cache (database).
- Why am I seeing heavy database load from WP LCache?
When you first enable WP LCache, you’ll have a good amount of database activity as it writes all cache entries to the database. Eventually, as long as your codebase is optimized, database activity will die down and most activity will be in APCu.
However, if your codebase isn’t optimized, you’ll see continued database load. Some common issues include:
- Frequent calls to
wp_cache_flush(), which empties the entire cache and requires the L2 to be completely repopulated.
- Redundant or duplicative calls to
wp_cache_set(), where code paths hardly ever use the cache values they set.
In both of these cases, any persistent object cache drop-in probably isn’t going to be useful until you solve your code problems.
- Frequent calls to
Laguntzaileak eta Garatzaileak
“WP LCache” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi.Laguntzaileak
0.6.1 (October 3rd, 2017)
- Switches back to
utf8for LCache tables [#149].
0.6.0 (August 28th, 2017)
utf8mb4as a database charset [#131,#143].
- Updates to LCache v0.4.0.
- Improve readme and grunt tasks [#130].
0.5.2 (May 3rd, 2017)
- Normalizes address key to comply with DB column length.
- Always runs database table initialization on the
- Doesn’t require APCu to be enabled in CLI.
- Test improvements.
0.5.1 (April 25th, 2017)
- Uses the correct DSN format in all DB_HOST scenarios.
- Only loads LCache library for PHP 5.6+, to ensure WordPress doesn’t fatal on older versions.
- Test improvements.
0.5.0 (November 2nd, 2016)
- Splits WordPress’ alloptions cache into separate cache keys to mitigate cache pollution caused by race conditions. See #31245 for further detail.
- Emits warnings in CLI when LCache isn’t properly configured.
- Incorporates a variety of test suite improvements.
0.4.0 (October 5th, 2016)
- Switches to stub file approach for enabling object cache drop-in, because symlink changes aren’t detected by opcode cache in PHP 5.5+.
0.3.1 (September 22nd, 2016)
- Updates LCache to v0.3.4, which automatically detects and handles misuse of the TTL as an expiration timestamp.
0.3.0 (September 21st, 2016)
- Introduces the
wp lcache enableWP-CLI command to create the
- Updates LCache to v0.3.2, which is more noisy about failed L2 serialization.
- Better admin notices: alerts when LCache database tables are missing, or if the plugin is active but
0.2.2 (September 14th, 2016)
- Updates LCache to v0.3.1, which has L2 cache guard against returning failed unserializations.
STRICT_ALL_TABLESon the database handler to fail and give warnings if there are issues with database inserts.
- Bug fix: Uses
LONGBLOBcolumn type for lcache_event
valuecolumn. Previously, the
BLOBwhich meant that long cache values (e.g. alloptions) could be unexpectedly truncated.
0.2.1 (September 14th, 2016)
- Bug fix: Properly flushes entire LCache with
wp_cache_flush()is called. Previously, LCache was called improperly, meaning none of the cache was flushed.
0.2.0 (September 14th, 2016)
- Updates LCache to v0.3.0, fixing issues with faulty expiration.
0.1.0 (September 7th, 2016)
- Initial release.