[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 tillkruess):

 Replying to [comment:13 sanchothefat]:
 > 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 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?

 It does not cause unnecessary cache requests. Please open a dedicated
 ticket for your problem, it's irrelevant to this ticket.

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