WordPress makes quite a bit of database calls to render a page. What the object cache does is to cache some of this data so it does not have to hit the database again for the same thing. WordPress has it’s own object cache you can enable, however it is not persistent, ie only caches data for a single page load. What GatorCache will do is store this data to disk so that it is persistent, further reducing the db load.
The object cache is not enabled by default, you’ll find the setting on the “General” settings tab beneath the page cache setting.
ok. Is there any danger if we try this ?
Should we watch for something ?
I would like to add that i use PHP 7.0.3 if it matters.
Well, it is a new feature, not really tested in production. I’ve tried it on a couple live sites, no issues thus far.
It’s more for interactive sites that can’t run a page cache since users are logged in. If most of your traffic hits a page cache, the object cache isn’t going to give a significant performance increase since it’s already bypassing most of WordPress and bypassing it altogether if you have http cache with htaccess.
Thanks. Crystal Clear.
I see a few problems already, so i disable it for now.
One of the problems, is that i deleted/uninstalled a plugin from the admin, and while it was actually removed, it showed as installed.
Thanks, would you mind creating a new support request with that so I make sure to address the issue with object cache and plugin deactivation?
It seems that when you enable object cache, there is some more debug information on the page source.
Here is one of mine:
<!– Cache Hits: 3859 | Cache Misses: 24 | Cache Disk Hits:135 –>
Not sure what it means and if it is good or bad.
The Home page seems excluded from object caching since the is no such info displayed.
Also the search pages seems to greatly benefit.
All in all, enabling object caching to my WP site, it appears to me faster and more “alive” (not logged in tests).
