[wp-trac] [WordPress Trac] #57625: WP_Query cache memory leak

[WordPress Trac]

#57625: WP_Query cache memory leak
--------------------------+------------------------------
 Reporter:  owi           |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Cache API     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  performance
--------------------------+------------------------------

Comment (by spacedmonkey):

 @owi It is worth noting, that caching can be disabled for WP Query if you
 so desire. See the original blog post.
 https://make.wordpress.org/core/2022/10/07/improvements-to-wp_query-
 performance-in-6-1/ . Until the fix is merged, then this might be best
 path forward.

 As for this issue. The point of an object cache, is should should allow it
 to fill up and the the object cache is in charge of how it decides to get
 rid of objects. The idea is to fill up the cache and let objects fall out
 of cache. Not all objects in cache should live forever, there should be
 evocation done at the object cache level ( memcache or Redis ). As notes
 in the description, a TTL for forever does not seem right. Posts and
 terms, may not change but other caches will only live until the last
 change value is updated.

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