SQLite Object Cache vs 站长帮 – WordPress CDN 缓存管理插件

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.

核心功能亮点 🚀 智能缓存刷新 – 文章/页面发布或更新时自动刷新相关 CDN 缓存 – 评论提交及审核通过后即时更新展示 – 支持首页、分类页、标签页等核心页面的缓存管理 ⚡ 手动刷新与预热 – 支持手动刷新指定 URL 的缓存 – 支持手动预热指定 URL 的缓存 – 独立操作页面，简单易用 🔧 多 CDN 服务商支持 – 腾讯云 CDN – 腾讯云 EdgeOne – Nginx ngx_cache_purge 模块 – Cloudflare 🛠️ 便捷管理 – 直观的中文管理界面 – 完善的错误日志系统 – 支持多场景刷新策略配置 🔌 扩展友好 – 采用模块化架构设计 – 预留多 CDN 服务商接口 – 持续更新维护 → 插件官方文档 安装指南 通过 WordPress 后台「插件」→「安装插件」上传安装 在插件页面点击「启用」 前往「设置」→「CDN 缓存管理」完成配置 在「主要设置」中勾选需要启用的 CDN 服务商 根据需求配置缓存刷新策略 常见问题 如何获取腾讯云 API 密钥？ 访问腾讯云 API 密钥管理控制台 创建密钥对 为什么缓存刷新失败？ 检查 API 密钥是否有效 确认网络连接正常 查看插件错误日志获取详细信息 参考故障排除指南 手动刷新和预热有什么区别？ 刷新缓存：清除指定 URL 的旧缓存，下次访问时重新从源站拉取 预热缓存：提前将指定 URL 的内容缓存到 CDN 节点，无需等待用户访问才缓存 哪些服务商支持预热功能？ 目前只有腾讯云 CDN 和腾讯云 EdgeOne 支持预热功能。Nginx 和 Cloudflare 不支持预热。 隐私声明 本插件仅通过官方 API 与 CDN 服务商交互，传输必要信息包括： – 需要操作的 URL 列表 – 用于身份验证的 API 密钥 – 操作类型标识符 我们不会收集或存储您的网站数据。 腾讯云服务隐私政策： https://cloud.tencent.com/document/product/301/11470 Cloudflare 隐私政策： https://www.cloudflare.com/zh-cn/privacypolicy/ 技术支持 由 站长帮 专业团队维护 在线支持：社区问答 – 站长帮教程：https://www.zhanzhangb.cn/tutorials/ – 站长帮资源：https://zy.zhanzhangb.cn/