[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:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.9
Component:  Cache API                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |  performance
-------------------------------------------------+-------------------------

Comment (by tillkruess):

 Replying to [comment:50 spacedmonkey]:
 > That approach relied on the object cache backend efficiently evicting
 stale caches. This worked well with memcache, but with other backends such
 as Redis, eviction behaviour is not always reliable.

 Instead I'd say:

 > That approach relied on the object cache backend evicting stale keys
 which is not always enabled by default (Redis/Valkey). Regardless of the
 keys eviction the behaviour caused tons of cache keys to generate, while
 the new approach will not.

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