[Resolved] Is it safe to use W3 Total Cache plugin on ToolSet?

[Author]

Posts

[PaulS4783]

I like the Toolset product so far, but I'm a bit concerned about the performance.

Is it safe to use a caching plugin like W3 Total cache?

Do you recommend any other techniques to improve performance?
I am using WPML with Toolset.

[Nigel]

Hi Paul

Views makes extensive use of caching internally where possible, which you can read a little more about here: https://toolset.com/documentation/user-guides/front-page-filters/how-to-use-views-parametric-search-on-large-sites/

Many of our users employ caching plugins successfully, although we don't have recommendations for any particular one.

The one particular area where we need to do better—and which is on our roadmap—is to give more control over what assets are loaded on what pages.

Right now Views tends to load various scripts and styles on all pages, because you may include a View on the page that needs them, and by the time the View is inserted in the build-process (e.g. in a footer widget) it can be too late enqueue the required assets. We aim to add more user control over what gets enqueued where.

Using a CDN will help with this, and a caching plugin will help subject to the usual limitations, that if the content is very dynamic, e.g. different users seeing different content, then the content needs to be generated each time and cannot be delivered from a cache. The speed of such pages will depend on their complexity, as well as the server resources.

[PaulS4783]

Thanks for the reply.
So just to confirm, the native Views caching is deactivated when WPML is active
(as per https://toolset.com/documentation/user-guides/front-page-filters/how-to-use-views-parametric-search-on-large-sites/ )

[Nigel]

Hi Paul

That's correct, when WPML is active Views internal caching is not used.

[PaulS4783]

thank you.