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

[WordPress Trac]

#57625: WP_Query cache memory leak
-------------------------------------------------+-------------------------
 Reporter:  owi                                  |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.3
Component:  Cache API                            |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch early commit has-unit-     |     Focuses:
  tests has-dev-note                             |  performance
-------------------------------------------------+-------------------------

Comment (by manos2000):

 with WP_REDIS_CACHE_TTL expired keys will be evicted before max memory
 reached?


 Replying to [comment:12 skithund]:
 > > There are other query caches that been in core for years, so is this
 such a problem now?
 >
 > You can see pretty clearly in my attached graph when we upgraded to WP
 6.0 on a busyish multisite WooCommerce installation. After couple of OOM
 hiccups on this site we added `WP_REDIS_CACHE_TTL` to WordPress and
 `maxmemory` to Redis as a quick-fix "eviction policy" to all our WP
 installations (200+).
 >
 > I still haven't found time to debug further what's the root cause for
 terms invalidating pretty much on every timed cron run. Possibly a badly
 behaving "Something for WooCommerce Pro" plugin.
 >
 > > There are 2 hard problems in computer science: cache invalidation,
 naming things, and off-by-1 errors.

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