Title: Cache system conflict
Last modified: April 26, 2018

---

# Cache system conflict

 *  Resolved [Jedi Black](https://wordpress.org/support/users/cihan1368/)
 * (@cihan1368)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/cache-system-conflict/)
 * Hi Hector,
 * We have about 1k+ real time traffic. We are using cache system(php-memcache ve
   memcached (service)) already, if any conflict possible we use both plugin and
   our cache system?
 * Thanks.
    -  This topic was modified 8 years, 1 month ago by [Jedi Black](https://wordpress.org/support/users/cihan1368/).

Viewing 1 replies (of 1 total)

 *  Plugin Author [Hector Cabrera](https://wordpress.org/support/users/hcabrera/)
 * (@hcabrera)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/cache-system-conflict/#post-10221001)
 * Hi [@cihan1368](https://wordpress.org/support/users/cihan1368/),
 * WordPress will use memcached to store data into memory for faster access and 
   to reduce the number of database operations. This shouldn’t have an impact on
   how WordPress Popular Posts operates.
 * So no, I don’t think that would be a problem 🙂

Viewing 1 replies (of 1 total)

The topic ‘Cache system conflict’ is closed to new replies.

 * ![](https://ps.w.org/wordpress-popular-posts/assets/icon-256x256.png?rev=1232659)
 * [WP Popular Posts](https://wordpress.org/plugins/wordpress-popular-posts/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-popular-posts/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-popular-posts/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-popular-posts/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-popular-posts/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-popular-posts/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Hector Cabrera](https://wordpress.org/support/users/hcabrera/)
 * Last activity: [8 years, 1 month ago](https://wordpress.org/support/topic/cache-system-conflict/#post-10221001)
 * Status: resolved