[wp-trac] [WordPress Trac] #59592: Store last changed value in key instead of using it as a salt for query caches

[WordPress Trac]

#59592: Store last changed value in key instead of using it as a salt for query
caches
--------------------------------------+-----------------------------
 Reporter:  spacedmonkey              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Cache API                 |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+-----------------------------

Comment (by sanchothefat):

 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.

 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?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59592#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform