How specific is seperate output cache by browser?

Kyle Sobus asked on March 20, 2018 14:45


If output cache is separate for each browser, how specific is this? Like Chrome, safari, firefox? Or Chrome 31? Chrome 31.2351(madeup version).

We are still on Kentico 8 on three of our sites if that makes a difference.

I want to be sure as many users as possible loading our site with output cache as opposed to compiling the page. (We have some webparts with some ridiculous queries at the moment.)

Thank you in advance!

Kyle Sobus

Recent Answers

Zach Perry answered on March 20, 2018 15:16

The only cache that should be browser specific is files, like css, js, that is all client side caching.

Output caching is server side, and it depends on how you set it up. You can read more of the documentation here

0 votesVote for this answer Mark as a Correct answer

Kyle Sobus answered on March 20, 2018 16:25

Hi Zach!

The output cache, is what I am referring to. On the page you referenced, the section, "Caching multiple output versions of pages" the output cache is created for each of the following parameters. * username * lang * browser * cookielevel * deviceprofile * domain * viewmod

The "browser" = "Different types of web browsers.", so that is the piece that concerns me. While I assume it is based on only the 'type', not the version, I want to be sure because there are many different versions out there.

0 votesVote for this answer Mark as a Correct answer

Peter Mogilnitski answered on March 20, 2018 17:03 (last edited on March 20, 2018 17:23)

Look at the documentation for version 8. The system stores different versions of the output cache for pages based on the selected variables (see System -> Performance -> Output caching). By default you have username;sitename;lang;browser;cookielevel;deviceprofile. For example, if you uncheck the 'username' option, pages use the same output cache data for all users (depending on the remaining variables). If you want to have something user specific - then you can to add substituion macros. For example you can use substituion macro to show who is logged in on top of the page (if this is the only portion of the page which is user specific) So the system gets the whole page from cache and replace this tiny portion on the top with logged in user.

Again it depends how your site is set up if you are using Bootstrap - you probably can remove browser and deviceprofile (media queries would take care of all that).

Less variables you have there more frequently your output cache is gonna be used.

P.S. The other thing to look at is Allow file system cache. So instead of keeping your pages in memory they will be kept on disc. Less memory footprint and faster server reloads. Anyway you have to play around with the settings and adjust them to your needs.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.