Title: Limits
Last modified: August 21, 2016

---

# Limits

 *  Resolved [daverage](https://wordpress.org/support/users/daverage/)
 * (@daverage)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/limits-1/)
 * Hi.
    Is there a limit to the number of pages that can be cached or at which point
   his becomes impractical. I have over 6000 pages on my site?
 * Thanks
 * [http://wordpress.org/extend/plugins/wp-fast-cache/](http://wordpress.org/extend/plugins/wp-fast-cache/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Website Launches](https://wordpress.org/support/users/taylorhawkes/)
 * (@taylorhawkes)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/limits-1/#post-3806092)
 * daverage,
 * Although there is technically no limit, I would say over 400 posts/pages will
   become impractical to manage. The plugin is so fast because it essentially “pre-
   builds” the pages. If you need to refresh all 400 pages the load on the server
   could be problematic.
 * I have site with about 1000 posts, and I use this plugin and just cache top 100
   recent posts and then all (27) of my pages.
 * I am looking into ways to make it more ideal for larger sites and still keep 
   it light weight.

Viewing 1 replies (of 1 total)

The topic ‘Limits’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-fast-cache.svg)
 * [WP Fast Cache](https://wordpress.org/plugins/wp-fast-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-fast-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-fast-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-fast-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-fast-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-fast-cache/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Website Launches](https://wordpress.org/support/users/taylorhawkes/)
 * Last activity: [12 years, 10 months ago](https://wordpress.org/support/topic/limits-1/#post-3806092)
 * Status: resolved