Description
Description
The configuration cache currently stores a timestamp as version:
https://github.com/neos/neos-development-collection/blob/master/Neos.Neos/Classes/ViewHelpers/Backend/ConfigurationCacheVersionViewHelper.php#L36
This is then used to do cache busting for requests in the Neos UI.
But when running multiple Neos instances in a Cluster this timestamp can be different for each instance and therefore every request might invalidate the caches again.
This leads to an increased loading time for the user.
This can be solved by storing the cache in Redis, but the question is, whether this is needed at all and couldn't just be solved by using a hash of the current configuration.
The configuration version cache is also flushed when accounts or sites are being edited.
I'm not sure how this affects the actual configuration.
Affected Versions
Neos: all
Activity