Configuration-Cache tab

File Registry

• Provides a significant boost in performance by mapping the whole framework and jReviews filesystem and caching it.
• You should clear the file registry often using the link on the left column if you are creating custom theme files with suffixes or adding new files to the jreviews_overrides folder. Otherwise jReviews is not able to find the new files.

Combine, Compress & Cache Javascript/CSS

• Enable JS Cache
  • What it does: All jReviews javascript files are combined, compressed and then stored in the cache to reduce the number of http requests and JS file size to improve site load time.
  • See Google Minifiy code for further explanation http://code.google.com/p/minify/

• Enable CSS Cache
  • What it does: All CSS javascript files are combined, compressed and then stored in the cache to reduce the number of http requests and CSS file size to improve site load time.
  • See Google Minifiy code for further explanation http://code.google.com/p/minify/
  • Notes: These two settings only optimize JReviews JS and CSS files, not the entire Joomla site. If you use another extension to optimize JS or CSS files it is best to disable these in JReviews.
  • These are separate settings because they work independent of each other. They also work independent of other components and the Joomla core. It is possible and common to use one of these features without enabling the other.

Cache Settings

• Cache duration (seconds) - cached files will be re-created if they have expired
• Enable Query Cache
  • The cache is cleared after the cache duration has passed or every time the JReviews setup, configuration, a listing or review is submitted or updated. This setting when enabled caches the data returned from the database for both guests and registered users. It reduces the number of queries per page for lists and detail pages, which have some of the most intensive queries.
  • Notes: The cached queries will take up disk space because all returned data is stored. If disk space is an issue, monitor it and it might make sense to leave it disabled. It's a trade off between database queries and disk storage. Query cache should be used in combination with a view cache solution to get improved results for registered users where view cache is typically disabled in both JReviews and Joomla.

• Enable View Cache (Guests Only)
  • Caches whole views for guest users only. The cache is cleared after the cache duration has passed or everytime the JReviews setup, configuration, a listing or review is submitted or updated.
  • Notes: This setting is similar to the Joomla Cache. The JReviews view cache is only for guests viewing the output of the JReviews component, not the entire site. If you are using the Joomla Cache or a 3rd Party Cache it may be best to turn off this cache.

• Notes on JReviews Cache Optimization in General:
  • If you enable debug mode in Joomla you can check the number of queries and memory used in the different pages and that gives you a reference for what happens when you enable/disable some of these settings.
  • When using another extension to compress JS or CSS files you may have to exclude some of the JReviews scripts from the optimization. After optimizing your sites be sure to check all functionality as a guest.