[wp-trac] [WordPress Trac] #64696: Real time collboration effectively disables persistent post caches while anyone edits a post

[WordPress Trac]

#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
--------------------------------------+--------------------------
 Reporter:  peterwilsoncc             |       Owner:  (none)
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  7.0
Component:  Posts, Post Types         |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by spacedmonkey):

 Sorry if I’m a bit late to this discussion. Since I worked on the WP_Query
 caching, I wanted to add a thought.

 If the concern is post meta invalidating caches, I think there’s a more
 targeted approach we could take.

 At the moment, we invalidate the entire post cache group whenever post
 meta is updated, which has always felt quite wasteful. In practice, post
 meta changes only matter for queries that actually join against the post
 meta table.

 Instead, we could introduce a separate “last changed” value specifically
 for post meta (and potentially other meta types in future). We would then
 only include this in the cache key when the query performs a join on the
 post meta table. For all other queries, the existing post “last changed”
 value should remain sufficient.

 I put together POC PR of this idea [https://github.com/WordPress
 /wordpress-develop/pull/11427 here].

 Would be interested to hear your thoughts on this.

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