Ideas on invalidation optimization #10
Description
Well, I have some ideas how the invalidation costs can be decreased a lot.
Also the CDN contents will stay faster most of the time because there is a lot of more caching and less warming up again :-)
I have managed to implement some of the things in my local enviroment but I cannot say if these changes would work in all possible enviroments. Complicated to say because of single- or multi-site configurations, single- or multi-domain settings, language fallbacks, detailed language configurations and so on.
Here are my suggestions:
-Invalidate only the caches of pages in languages, which are activated (active site languages, not page languages). Currently all are invalidated also for inactive languages.
-Invalidate only caches of the site, which contains the changed page. I managed to get this running by adding a typoscript snippet on each top level site which only contains a single distribution id. Before all in the backend configured distributions got invalidations for a change on a page of one site.
-Invalidate the page cache only for the current language if the content element is in a specific language and not in "All languages".
Othervise clear all language urls for this page.
-Invalidate the page cache only for pages which are not hidden.
We have a few hundred pages and a just a few editors but the invalidations are exploding a bit. Hopefully this can help someone.