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

 Thanks for the clarification. I’m not talking modifying any db queries
 fwiw, but the impact on remote cache servers does feel relevant still.

 Definitely a smart move where it’s only a small amount more data, just IDs
 retrieved at the same time, though for user, post or term queries
 returning a lot of rows (not good practice but happens) it could be a lot
 more data. I’ll see if I can pull some stats for that in case it’s
 helpful.

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