Title: Why not use wordpress cache api?
Last modified: August 21, 2016

---

# Why not use wordpress cache api?

 *  [Calin Don](https://wordpress.org/support/users/calin/)
 * (@calin)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/why-not-use-wordpress-cache-api/)
 * Hi,
 * Are there any plans to support caching using wrodpress cache api?
 * The current approach, using files makes it difficult to scale because if you 
   have multiple wordpress nodes behind a load balancer and the filesystem is not
   shared you end up having two separate caches.
 * WP cache api on the other hand has support for memcache or redis which can be
   shared between multiple instances.
 * [http://wordpress.org/plugins/role-scoper/](http://wordpress.org/plugins/role-scoper/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Kevin Behrens](https://wordpress.org/support/users/kevinb/)
 * (@kevinb)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/why-not-use-wordpress-cache-api/#post-4116160)
 * No, if you have issues with the internal cache I recommend disabling it or migrating
   to Press Permit, which has simpler queries and no caching.

Viewing 1 replies (of 1 total)

The topic ‘Why not use wordpress cache api?’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/role-scoper.svg)
 * [Role Scoper (Obsolete - Please install PublishPress Permissions)](https://wordpress.org/plugins/role-scoper/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/role-scoper/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/role-scoper/)
 * [Active Topics](https://wordpress.org/support/plugin/role-scoper/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/role-scoper/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/role-scoper/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Kevin Behrens](https://wordpress.org/support/users/kevinb/)
 * Last activity: [12 years, 8 months ago](https://wordpress.org/support/topic/why-not-use-wordpress-cache-api/#post-4116160)
 * Status: not a support question