Try our conversational search powered by Generative AI!
AI OnAI Off
HttpCachability caching
As far as I know there are not any specific drawbacks. You should use cachability with the setting server, this can be found in application settings in configfiles.
Not answer to all your questions... :/
You can have a look at this website from a member of the Pro Service team at episerver: http://epiwiki.se/developing/performance/common-performance-mistakes-when-developing-for-episerver
Edited,
May 22, 2014 11:31
Hi,
Im looking at using httpCachability and storing the cache data on the Server. Are there any draw backs to using this method of Caching? Can this be used on a 4 server load balanced farm?
I have noticed that once I click around the site once, the site is cached and the site's performance has improved considerably - however, when I do either a Save or Publish to content the whole cache is deleted from the server and the site goes slow once again, until cached.
Is there a way to configure this Deletion to only Published content and NOT saved content?
Or, can anyone recommend an alternative way to cache - I have looked into IIS and it doesnt really improve the performance much.
Jon