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

 > @ellatrix @joehoyle: maybe it would help to have non auto-loaded meta
 data, but I think that would be a larger change and warrant another
 ticket. While I opened the ticket because of the effects on cache, I think
 the new table is a better solve for the issue at hand and allows us to
 avoid altering the Query and meta APIs.

 How would it be a larger change than adding a whole new table? 🤔 I
 quickly tried this locally and I have `113 insertions(+), 14 deletions(-)`
 versus `+3,887 -1,436` for the currently open database table PR. But I may
 be missing something. I think the only thing we need there is a new
 `register_post_meta` setting, and some early returns in
 `wp_cache_set_posts_last_changed` and `WP_Meta_Query`. What am I missing?

 Also, I'm not sure I understand why would it require a new ticket? It
 seems directly applicable here. Why is adding a few lines to Query and
 meta APIs bad?

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