Thank you for using this with a large site! I don’t have large site benchmarks to offer you, so I would be grateful if you would send me yours, maybe by posting them here.
As for SQLite doing memory caching, my code uses Write-Ahead Logging in SQLite. This provide a mixture of RAM caching and file system use. Using this plugin drives up per-php-fpm-process RAM usage and IOPS. That could get costly in server-provisioning charges.
What’s the “Total cost of operation” including RAM, IOPS, and administrative time / hassle? I hope you’ll contribute some real-world experience to helping understand that.
The plugin’s Statistics panel shows descriptive statistics about time taken for cache operations. I find the 95th percentile stats useful. If you can think of anything else the plugin should measure, please let me know.
It would also be great to hook up the stats measurement in the plugin to monitoring tools like Nagios or Cacti or whatever. I don’t know enough about those tools to specify that interface myself. If somebody who DOES know about that kind of tool will tell me what to implement, I’ll do it.
I created a screenshot of the performance stats. I have nothing to compare it to, but it’s humming along fine so far. It’s not very scientific, but the site doesn’t seem to be slower or faster than with the Redis object cache.
The cache and wall files are around 22MB each (after running for half a day).
Another plus for this plugin is that it also works on the staging copy of my site. The Redis object cache always complains about a foreign drop-in or something; plus, you don’t want to pollute your cache with staging data anyway. This plugin is nicely contained in the current directory tree. In addition, I reckon it’s easier to migrate a site to another server; it will even migrate the cache 🙂 It just makes things less complicated.
- This reply was modified 15 hours, 25 minutes ago by .
- This reply was modified 15 hours, 1 minute ago by .
Thanks for this information!
And, be careful to put your cache on local SSD / HDD storage, not a remote, shared, or NFS drive. /tmp is a good choice. Explanation about how to do that is here.