Context Navigation

Changes between Initial Version and Version 1 of Ticket #59592, comment 13

-                      initial
+                      v1
 Cross posting here from LinkedIn - an issue we hit with the recent core cache changes around option caching was really detrimental to performance because we’re using an object cache running on another server, a redis instance in our case. This isn't uncommon for larger sites.
 Each cache lookup is still a remote request, so while often faster than a heavy db query the current system also optimises for not making too many cache requests when we know it could be stale.
+Each cache lookup is still a remote request, so while often faster than a heavy db query ideally core would also optimise for not making too many cache requests when we know the data is likely to be stale.
 This approach sounds like it might cause the same problem so I’m curious about that consideration and whether you have benchmarks for our kind of setup too?
+This approach sounds like it might cause a lot of unnecessary cache requests, and cause us the same problem so I’m curious about that consideration and whether you have benchmarks for our kind of setup too?