Static Site Generator vs SQLite Object Cache

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.

Requires This plugin only supports execution from the command line using WP-CLI. Generate Generated static site with WP-CLI command. Replaces URLs or strings in content. Supports custom post types. Outputs the archive page for the year, month, and day. Outputs category archives. Outputs tag archives. Outputs author archives. Outputs feed. Outputs categories feed. Outputs tags feed. Sitemap by default in WordPress. Generates a file from a specified URL. Copy Copy the files that the following tags in the html read to the static site. ... CSS WP-CLI 1st argument(string) : /home/www/localhost.test : output path of full path 2nd argument(string) : https://localhost.test : url of output homepage optional argument1(string) : --cb1="site.com" --ca1="localhost.test" : cb1 -> Original string | ca1 -> Changed string optional argument2(string) : --cb2="/wordpress" --ca2="/" : cb2 -> Original string | ca2 -> Changed string optional argument3(bool) : --s : Only arguments 4-7, which directly specify the URL and file name, are executed. optional argument4(string) : --file1="ja/feed/index.xml" --orgurl1="https://site.com/ja/feed/" : file1 -> Output filename | orgurl1 -> Original url optional argument5(string) : --file2="ja/category/whatsnew-ja/feed/index.xml" --orgur2="https://site.com/ja/category/whatsnew-ja/feed/" : file2 -> Output filename | orgurl2 -> Original url optional argument6(string) : --file3="feed/googleimagesitemap/index.xml" --orgurl3="https://site.com/feed/googleimagesitemap/" : file3 -> Output filename | orgurl3 -> Original url optional argument7(string) : --file4="feed/googlevideossitemap/index.xml" --orgur4="https://site.com/feed/googlevideossitemap/" : file4 -> Output filename | orgurl4 -> Original url optional argument8(bool) : --c : Outputs file copy status to the console. Example1 wp static /home/www/localhost.test https://localhost.test Example2 wp static /home/www/localhost.test https://localhost.test --cb1="site.com" --ca1="localhost.test" --cb2="/wordpress" --ca2="/" In the html or xml, the original home page is converted to “https://localhost.test”, “site.com” is converted to “localhost.test”, and “/wordpress” is converted to “/”.