[wp-trac] [WordPress Trac] #23059: if object cache entry for last_changed in term and comments groups is purged, it invalidase too many cached items

[WordPress Trac]

#23059: if object cache entry for last_changed in term and comments groups is
purged, it invalidase too many cached items
--------------------------+------------------------------
 Reporter:  mark-k        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Cache         |     Version:  3.5
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by mark-k):

 Replying to [comment:2 ryan]:

 > Invalidating the caches is the entire purpose of last_changed. When
 anything term related is changed, last_updated is bumped and all term
 related query caches are passively invalidated as a result. Caches with
 old last_updated values will eventually be pushed out of the cache and
 garbage collected.

 1. Right now it invalidates too much. In my case it simply rendered object
 caching useless

 2. In practice it doesn't invalidate, as the value is set only once and
 unless it is purged from the cache by the caching software itself the
 value never changes no matter how many term related changes where done.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23059#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software