Docket Cache - Object Cache Accelerator

Object caching stores database query results so they can be retrieved quickly the next time they are needed. Cached data is served directly from the cache rather than making repeated database queries. This reduces the load on your server and makes your site faster. In simple terms, object caching keeps frequently used data in a location where it can be accessed more quickly.

By default, the WordPress object cache is non-persistent. This means cached data is stored in memory only for the duration of a single page request. It is not kept between page loads. To make it persistent, the object cache must be stored on disk. Docket Cache does more than just store the object cache — it converts cached data into plain PHP code. This is faster because WordPress can use the cache directly without additional processing.

OPcache is a caching engine built into PHP. It improves performance by storing precompiled script bytecode in shared memory, so PHP does not need to load and parse scripts on each request. Docket Cache converts the object cache into plain PHP code. When reading and writing cache data, it uses OPcache directly, which results in faster data retrieval and better performance.

Cronbot is an external service that pings your website every hour to keep WordPress Cron running actively. This service is optional and is not required. By default, it is not connected to the end-point server. You can disable it entirely on the configuration page.

The Garbage Collector is a scheduled event that runs every 5 minutes to monitor cache files, clean up expired entries, and collect statistics.

A RAM disk uses your server's memory (RAM) to act as a storage drive. It can be a hardware device or a virtual disk. Reading and writing data from RAM is much faster than from an SSD. Storing Docket Cache files on a RAM disk can greatly improve performance. Please note that creating a RAM disk requires server administrator access (root), so this option is not available on shared hosting. Here is an example command to create and use a RAM disk with Docket Cache: $ cd wp-content/ $ sudo mount -t tmpfs -o size=500m tmpfs ./cache/docket-cache To mount the cache path automatically when the server starts, update your /etc/fstab file. For more information about RAM disks:

1. How to Easily Create a RAM Disk
2. What Is /dev/shm and Its Practical Usage
3. Creating a Filesystem in RAM

By default, WordPress sets the memory limit to 256 MB. When combined with MySQL and the web server, you need more than 256 MB. If your hosting plan only provides 256 MB in total, this is not enough, and Docket Cache will not be able to improve your site's performance.

Docket Cache is an Object Cache Accelerator. It optimises caching by handling post queries, comment counting, WordPress translations, and more before storing the object cache.

Yes and no. You can use it together with a page caching plugin, but not with another object cache plugin.

Yes. The LiteSpeed Cache plugin includes its own Object Cache feature. It may display a notice asking you to disable Docket Cache. Simply turn off the LiteSpeed Cache Object Cache to use Docket Cache instead.

It is not recommended for high-traffic WooCommerce stores. Docket Cache is designed as a file-based alternative to in-memory caches like Redis and Memcached, and may not handle the demands of a busy store. For WooCommerce sites with heavy traffic, we recommend using Redis instead.

You can, but if your VPS supports Redis, we recommend using Redis for better performance. Docket Cache is best suited for environments where Redis or Memcached is not available. That said, Docket Cache works well for small to medium sites on a VPS, with no network connection required and no risk of cache-key conflicts.