[wp-trac] [WordPress Trac] #36953: Meta lazyloading can cause excessive calls to object cache

[WordPress Trac]

#36953: Meta lazyloading can cause excessive calls to object cache
-------------------------------------------------+-------------------------
 Reporter:  boonebgorges                         |       Owner:
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  4.6
Component:  Query                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug needs-unit-tests      |     Focuses:
  has-patch                                      |  performance
-------------------------------------------------+-------------------------

Comment (by boonebgorges):

 > So was term_meta_lazyload depreciated in WP 4.5?

 No. Term meta lazyloading was introduced in 4.5.

 > @boonebgorges The patch implements option #1 that you've listed as far
 as I can understand

 Thanks. I mistyped - I meant that the value of `lazyload_term_meta` should
 fall back on the value of `update_term_meta_cache`.

 > What I'm missing I guess is why a site can't just set
 update_term_meta_cache to "false" in the pre_get_posts call back?

 This can already be done. But it makes it impossible to prime the term
 cache without priming the termmeta cache.

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