Object Disk Cache drawbacks in production

Hello @saeesh

Thank you for your iqnuiry and I am happy to assist you with this.
Database caching can make your site faster if the time needed to get data from the database is more than the time needed to get data from the cache.
So, if you are on shared hosting, then RAM-based caching is likely to be unavailable for you. And disk-based caching is not that efficient. In other words, if you are on shared hosting, it’s recommended not to use database caching.
Object Cache allows getting data from the database more efficiently. Its purpose is similar to what Database Cache does. But compared to Database Cache, Object cache is more efficient as it allows us to process fewer requests.
As a rule of thumb, Object Cache is not worth using on shared hosting for the same reason as Database Cache, i.e. database is often not the performance bottleneck, but disk input-output operations.
However, like Database Cache, it can be beneficial to use if you are on VPS or a dedicated server, get a lot of traffic, have a lot of comments. Also, if you know that database is the bottleneck of your website performance, then Object Cache (like Database Cache) is beneficial to use. But in this case, it’s recommended to use Opcode, Memcached, or Redis options.
Thanks!

@ vmarko We are using AWS EC2 server instances and not shared hosting. We discarded redis because there were some security concerns and larger RAM needed. Will object caching via disk not be efficient to use?

Hello @saeesh

It may be efficient and maybe not. depends if that’s a bottleneck of your performance. Memory-based solutions are more efficient for DB and Object Caching. OC can create a lot of files on your disk.
As I mentioned before if the time needed to get data from the database is more than the time needed to get data from the cache it can be beneficial so you should give it a try then.
Thanks!