WordPress.org

1. Matt_NY
   Member
   Posted 2 years ago #

   <!-- Dynamic page generated in 57.190 seconds. -->
   <!-- Cached page generated by WP-Super-Cache on 2010-05-25 13:33:12 -->

   Something bad happening, pages load too slow for the first time (probably, when cache is being generated). On the second it flys.

   Used 2 plugins
   wp-super-cache (http://wordpress.org/extend/plugins/wp-super-cache/)
   wp-file-cache (http://wordpress.org/extend/plugins/wp-file-cache/)

   If I switch of wp-super-cache site loads straight.

   Maybe, super-cache trys to cache all the wp-file-cache files?

   Any idea, how to fix this?

   Thanks.

2. Vladimir Kolesnikov
   Member
   Posted 1 year ago #

   Hi Matt,

   WP Super Cache and WP File Cache are completely different plugins in what they cache.

   WP Super Cache is a page level cache plugin - that is, it caches the whole page and on subsequent requests it just sends the cached page to thje user bypassing WordPress and slow queries. The advantage of this approach is that WP Super Cache is extremely fast, disadvantage is that you lose all dynamics.

   WP File Cache is an object level cache plugin - it caches only those objects which it is explicitly asked to. That is, the plugins/theme must be coded to use WordPress Cache API. WordPress core uses WP Cache API, but third party plugins may not use it. In this case if those plugins are slow, WP File Cache won't help - it cannot force the plugins to use the API.

   Both plugins can coexist together and WP File Cache can help WP Super Cache when it comes to cache generation.

   As for your question, could you please clarify the following: what happens when:

   1. Super Cache is on, File Cache is off;
   2. Super Cache is off, File Cache is on;
   3. both are on?

   Thank you in advance.

3. Matt_NY
   Member
   Posted 1 year ago #

   If I remove wp-file-cache nothing changes.

   When I switch off wp-super-cache site becomes to load straightly.

4. Vladimir Kolesnikov
   Member
   Posted 1 year ago #

   Well, sounds like the problem is in WP Super Cache.

Topic Closed

This topic has been closed to new replies.