[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 joehoyle):

 Perhaps the simplest solution here would be to add a flag to
 `register_meta` for `causes_last_changed_update` which determines if we
 bump the `wp_cache_get_last_changed` value on updating the meta.

 As @ellatrix mentioned, a WP_Query should then not allow querying by
 meta_value for those types of registered meta to prevent accidental cache
 use.

 In the future I think it would be good to be able to register a meta-key
 as non-autoloded too so prime_post_caches doesn't pull those meta keys
 from the DB and store them in the single object-cache entry for all meta.
 I'm not sure that's needed immediately here, but I would imagine it could
 become a problem: currently storing anything more than ~ 1+ MB in a post's
 meta can cause significant issues with performance with persistent object
 caches.

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