Config changes invalidating cache
If you set the affects the permanent memory taken up by the cache.If the caches grow too large, they may crowd out transient session memory and slow down the system.This can yield enormous performance improvements, since the script used to generate the dynamic output does not need to run for each request.The cache can vary the output that is cached based on query string values as well as HTTP headers sent from the client to the server. Sitefinity exposes a class called and, if you wanted to inject dynamic content onto cached pages, you can take advantage of this infrastructure without hindering performance. You can disable caching page by page and you can also leverage the post-cache substitution mechanism.
For more information, see For developers: Use a cache substitution widget.Cache tracing can show which caches fill quickly for your specific server usage pattern.Each cache is configured in an XML block with the following parameters: controls the maximum size of the cache.Until before this issue, Config objects (which are the "things" representing the various pieces of configuration in the Configuration System in Drupal 8) did not have associated cache tags.Nor did they invalidate cache tags upon update or deletion. Configuration entities are a layer on top of the configuration system, you could look at them as wrapped config objects, supporting more complex use cases, and with the same cache tag support that all entities have.
If you want to invalidate selected objects but your users don't necessarily access every object on your origin, you can determine which objects viewers have requested from Cloud Front and invalidate only those objects.