SQLite Object Cache vs WEDOS | Protection & Cache Performance

A persistent object cache helps your site perform well. This one uses the widely available SQLite3 extension, and optionally the igbinary and APCu extensions to php. Many hosting services offer those extensions, and they are easy to install on a server you control. What is this about? 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 page cache; 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. 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. Who should use this? If your site runs on a single web server machine, and that server provides the SQLite3 and igbinary extensions to php, this plugin will almost certainly make your site work faster. And if that server provides the APCu extension, this plugin uses it too. Some hosting providers offer redis cache servers. If your provider offers redis, it may be a good choice. You can use it via the Redis Object Cache plugin. Sites using redis have one SQL database and another non-SQL storage server: redis. Other hosting providers offer memcached, which has the Memcached Object Cache plugin. And some large multipurpose cache plugins, such as the LiteSpeed Cache, also offer object caching based on one of those cache server software packages. 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. But, for single-server site configurations, SQLite, possibly assisted by APCu, performs well. And the vast majority of sites are single-server. APCu APCu 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. Please look at Installation to learn how to configure this plugin to use APCu. The plugin works fast without it, and faster with it. 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. WP-CLI You can control this plugin via WP-CLI once you activate it. Please type this command into your shell for details. wp help sqlite-object-cache Credits 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. Props to Matt Jones for finding and fixing a bug that appeared on a heavily loaded system. Thanks to Massimo Villa for testing help, and to nickchomey for a comprehensive code review. 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. How can I learn more about making my WordPress site more efficient? We offer several plugins to help with your site’s database efficiency. You can read about them here.

Activate WEDOS Global protection — WAF, DDoS protection and CDN for your WordPress website. WEDOS Global (CDN Cache & Security) WEDOS Global Protection plugin helps site administrators activate WEDOS.protection from inside WordPress. The plugin provides a simple landing page for non-technical users, guided website and DNS setup, a dashboard with protection status, and a consent step before any external service activation request is sent. Cloud WAF & DDoS Protection By filtering traffic and blocking harmful cyberattacks on cloud servers, our WAF provides protection for your WordPress websites without putting any extra load on your local resources. Global CDN Cache The WEDOS Global CDN will ensure a significant increase of your WordPress loading speed, and better overall server response all around the world. Links to Documentation and Other Sources WEDOS Global Knowledge Base Community Help External Services This plugin connects to the following external services: WEDOS Global Protection (plugin.wedos.global) Verify domain ownership via a local verification file Register and activate the domain protection service Check the protection and DNS status Data sent: domain name, server IP address, admin email address, unique request ID. No personal visitor data is ever transmitted. WEDOS CDN (wp-cdn.wedos.com) Serves WordPress core and WooCommerce static assets (JS, CSS) from WEDOS CDN edge nodes Fetches a manifest file listing available asset versions and their SHA-256 hashes Assets are only rewritten when local file hash matches the CDN manifest — no data about visitors is transmitted CDN is opt-in and can be disabled at any time from the dashboard Anonymous telemetry (plugin.wedos.global/cdn-plugin/telemetry.php) Sends anonymous usage statistics once daily when opted in: plugin version, WordPress version, rewrite count No domain name, no IP address, no personal data is included Subscription management (plugin.wedos.global) Used only when you start a free trial or subscribe to a paid plan (Standard, Premium) Data sent: domain name, admin email address, selected plan identifier Subscription status is queried periodically to determine which paid features (e.g. detailed visitor geography) are unlocked The free plan does not require any subscription data exchange Billing provider (FastSpring) When you purchase a paid plan, your order is processed by FastSpring (fastspring.com) FastSpring acts as the merchant of record for the transaction See FastSpring’s privacy policy for details on data they collect during checkout Bundled Third-Party Libraries The plugin ships with the following open-source libraries (no external network calls — all bundled locally): Chart.js 4.4.0 (MIT license) Used for analytics charts (requests over time, top countries bars) Source: https://www.chartjs.org/ License: https://github.com/chartjs/Chart.js/blob/master/LICENSE.md jsvectormap 1.7.0 (MIT license) Used to render the interactive world map in the Visitor Geography section (paid feature only — loaded when geographic analytics are unlocked by the active plan) Source: https://github.com/themustafaomar/jsvectormap Map data renders aggregated country traffic counts received from the WEDOS Global Protection backend; no visitor data is sent anywhere License: https://github.com/themustafaomar/jsvectormap/blob/master/LICENSE The service is provided by WEDOS Group SA, 7 Rue Robert Stumper, L-2557 Luxembourg, EU. Terms of Service Privacy Policy By activating the plugin and clicking “Create request”, you explicitly consent to your domain data being sent to the WEDOS Global Protection service.