If we flush the config cache, the cache is build up by the customer in the frontend. The problem is that a lot of customer build the same cache and it took a lot of server resources.
Is there a smart way to build the config cache?
Something like, build a parallel config cache and switch it with the real cache keys?
Or just rebuild every config cache key in the adminhtml without flushing it?
We are using Redis as backend cache.
Edit: I figured out, that it's just the case if the cache key
CONFIG_GLOBAL_STORES_[A-Z]_[A-Z] is flushed.