A persistent object cache helps your site perform well. This one uses the widely available SQLite3 extension to php. Many hosting services offer it. If your hosting service does not provide memcached or redis, you may be able to use this plugin instead and get the benefit of object caching.
Caches 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 memoization cache.
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.
Thanks to Till Krüss. His Redis Object Cache plugin serves as a model for this one. And thanks to Ari Stathopoulos and Jonny Harris for reviewing this. (All defects are, of course, entirely the author’s responsibility.)
And thanks to Jetbrains for the use of their software development tools, especially PhpStorm. 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.
Installing “SQLite Object Cache” can be done either by searching for “SQLite Object Cache” via the “Plugins > Add New” screen in your WordPress dashboard, or by using the following steps:
- Download the plugin via WordPress.org
- Upload the ZIP file through the ‘Plugins > Add New > Upload’ screen in your WordPress dashboard
- Activate the plugin through the ‘Plugins’ menu in WordPress
The plugin offers optional settings for your
wp-config.php file. If you change them, deactivate the plugin first, then change them, then reactivate the plugin.
- WP_SQLITE_OBJECT_CACHE_DB_FILE. This is the SQLite file pathname. The default is …/wp-content/.ht.object_cache.sqlite. Use this if you want to place the SQLite cache file outside your document root.
- WP_SQLITE_OBJECT_CACHE_TIMEOUT. This is the SQLite timeout in milliseconds. Default: 5000.
- WP_SQLITE_OBJECT_CACHE_JOURNAL_MODE This is the SQLite journal mode. Default: ‘WAL’. Possible values DELETE | TRUNCATE | PERSIST | MEMORY | WAL | NONE.
Does this work with a multisite WordPress installation?
Yes. To see the Settings page, choose Settings > Object Cache from the first site, or any site, in the multisite installation.
How much faster will this make my site?
Exactly predicting each site’s speedup is not possible. Still, benchmarking results are promising. Please see this. If you run a benchmark, please let the author know by leaving a comment on that page or using the support forum.
What Cached Data Size should I use for my site?
The default setting for Cached Data Size is 4 MiB. This plugin allows the actual cached data size to grow larger than that, and occasionally removes old data to trim back the size to the setting. Take a look at the Statistics page. If your actual cached data setting is consistently larger than the setting, double the setting.
If you operate a large and busy site, try an initial setting of 32 MiB, then adjust it based on the growth of the actual size.
What is SQLite?
SQLite is fast and efficient database software. It doesn’t require a separate server. Instead, it is built into php using the SQLite3 extension. SQLite programs don’t need to open network connections to send requests and wait for replies.
Does this plugin replace MariaDB or MySQL with SQLite?
No. Your MariaDB or MySQL database sql server still holds all your content. All your site’s imports, exports, backups and other database operations continue to function normally. This plugin uses SQLite simply to hold named values. For example, a value named “post|3” will hold a temporary, easy-to-retrieve cached copy of post number 3. When it needs that post, WordPress can fetch it quickly from SQLite.
Wait, what? Do I really need two different kinds of SQL database?
No, you don’t. This plugin doesn’t use SQLite as a full-fledged database server.
A persistent object cache needs some kind of storage mechanism. SQLite serves this plugin as a fast and simple key / value storage mechanism.
Some hosting providers offer scalable high-performance redis cache servers. If your provider offers redis, it is a good choice. You can use it via Redis Object Cache plugin. Sites using redis have one SQL database and another non-SQL storage scheme: redis. Other hosting providers offer memcached, which has the Memcached Object Cache.
But many hosting providers don’t offer either redis or memcached, while they do offer SQLite. This plugin enables your site to use a persistent object cache even without a separate cache server.
Is this plugin compatible with my version of MySQL or MariaDB?
Yes. It does not require any specific database server version.
Is this plugin compatible with my version of redis or memcached?
Why not use the site’s main MariaDB or MySql database server for the object cache?
In WordPress, as in many web frameworks, your database server is a performance bottleneck. Using some other mechanism for the object cache avoids adding to your database workload. Web servers serve pages using multiple php processes, and each process handles its own SQLite workload while updating a shared database file. That spreads the object-cache workload out over many processes rather than centralizing it.
Do I have to back up the data in SQLite?
No. It’s a cache, and everything in it is ephemeral. When WordPress cannot find what it needs in the cache, it simply recomputes it or refetches it from the database.
To avoid backing up SQLite files, tell your backup plugin to skip the files named
This plugin automatically suppresses backing up your SQLite data when you use the Updraft Plus, BackWPUp, or WP STAGING plugins. The Duplicator plugin does not offer an automated way to suppress copying those files.
If you use some other backup or cloning plugin, please let the author know by creating a support topic.
If I already have another persistent object cache, can I use this one?
No. You only need one persistent object cache, and WordPress only supports one.
If I operate a scaled-up load-balanced installation, can I use this?
No. If you have more than one web server this doesn’t work correctly. If you operate at that scale, use redis or some other cache server. (If you aren’t sure whether you have a load-balanced installation, you almost certainly do not.)
Can I use this with the Performance Lab plugin?
Yes, but you must activate this plugin first before you activate Performance Lab. And, you must deactivate Performance Lab before deactivating this plugin last.
The Performance Lab plugin offers some advanced and experimental ways of making your site faster. One of its features uses object-cache initialization code to start tracking performance. So there’s a required order of activation if you want both to work.
How can I use this object cache to make my plugin or theme code run faster?
Use transients to store your cacheable data. WordPress’s Transient API uses persistent object caching if it’s available, and the MariaDB or MySQL database when it isn’t. The Metadata API and Options API also use persistent object caching.
How does this work?
This plugin uses a WordPress drop-in to extend the functionality of the WP_Cache class. When you activate the plugin it creates the dropin file
.../wp-content/object-cache.php. Upon deactivation, it removes that file and the cached data.
Where does the plugin store the cached data?
It’s in your site’s
wp_contentdirectory, in the file named
.ht.object-cache.sqlite. That file’s name has the
.ht.prefix to prevent your web server from allowing it to be downloaded. SQLite also sometimes uses the files named
.ht.object-cache.sqlite-wal, so you may see any of those files.
On Linux and other UNIX-derived operating systems, you must give the command
ls -ato see files when their names begin with a dot.
I want to store my cached data in a more secure place. How do I do that?
Putting your .sqlite files outside your site’s document root is good security practice. This is how you do it. If you define the constant
wp_config.phpthe plugin uses that for sqlite’s file pathname instead. For example, if
wp-config.phpcontains this line
define( 'WP_SQLITE_OBJECT_CACHE_DB_FILE', '/tmp/mysite-object-cache.sqlite' );
your object cache data goes into the
/tmpfolder in a file named
You can also define
WP_CACHE_KEY_SALTto be a text string. Continuing the example, this line
define( 'WP_CACHE_KEY_SALT', 'qrstuv' );
causes your object cache data to go into the
/tmpfolder in a file named
Can this plugin use SQLite memory-mapped I/O?
Yes. You can use your OS’s memory map feature to access and share cache data with SQLite Memory-Mapped I/O. On some server configurations this allows multiple php processes to share cached data more quickly. In the plugin this is disabled by default. You can enable it by telling the plugin how many MiB to use for memory mapping. For example, this wp-config setting tells the plugin to use 32MiB.
define( 'WP_SQLITE_OBJECT_CACHE_MMAP_SIZE', 32 );
Notice that using memory-mapped I/O may not help performance in the highly concurrent environment of a busy web server.
I sometimes get timeout errors from SQLite. How can I fix them?
Some sites occasionally generate error messages looking like this one:
Unable to execute statement: database is locked in /var/www/wp-content/object-cache.php:1234
This can happen if your server places your WordPress files on network-attached storage (that is, on a network drive). To solve this, store your cached data on a locally attached drive. See the question about storing your data in a more secure place. It also can happen in a very busy site.
Why do I get errors when I use WP-CLI to administer my site?
Sometimes WP-CLI commands issued from a shell run with a different user from the web server. This plugin creates one or more object-cache files. An object-cache file may not be readable or writeable by the web server if it was created by the wp-cli user. Or the other way around.
On Linux, you can run your WP-CLI shell commands like this:
sudo -u www-data wp config listThis ensures they run with the same user as the web server.
What do the Statistics mean?
Please read this.
Is there a joke somewhere in this?
Q: What are the two hardest things to get right in computer science?
- Caching things.
- Naming things.
- Coping with off-by-one errors.
Seriously, the core of WordPress has already worked out, over years of development and millions of sites, how to cache things and name them. This plugin simply extends that mechanism to make those things persistent.
I have another question
Contributors & Developers
“SQLite Object Cache” is open source software. The following people have contributed to this plugin.Contributors
- Clean up in chunks in an attempt to reduce contention delays and timeouts.
- Do PRAGMA wal_checkpoint(RESTART) when cleaning up, and also occasionally, to prevent the write-ahead log from growing without bound on busy systems.
- Retry three times if cache updates time out.
- Increase default cache size to 16MiB for new users.
- php 8.1, php 8.2 compatibility.
- Support for WordFence and other code using the object cache after shutdown.
- Support SQLite Memory-Mapped I/O.
- Reduce contention delays by limiting the number of get_multiple, set_multiple, add_multiple, and delete_multiple items in each transaction.
- Reduce index page fragmentation by using key order for set_multiple and add_multiple operations.
- Fix initialization defect in cache deletion. Props to @gRoberts84.
- Avoid VACUUM except on cache flush, and do it only with maintenance mode enabled.