[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          |     Focuses:  performance
-------------------------------+--------------------------

Comment (by peterwilsoncc):

 Replying to [comment:5 westonruter]:
 > I don't mean for //all// post meta additions and updates. I mean
 specifically in `WP_Sync_Post_Meta_Storage::set_awareness_state()` and
 `WP_Sync_Post_Meta_Storage::add_update()`.
 >
 > Here's what I have in mind: https://github.com/WordPress/wordpress-
 develop/pull/11002
 >
 > The only post meta involved would be `wp_sync_awareness` and
 `wp_sync_update`. I don't believe there are any queries introduced which
 involve querying by these post meta.

 Yep that makes more sense but I'd be hesitant doing so for a couple of
 reasons:

 * it adds a bug trap for our future selves, ie WordPress contributors, due
 to the snowflake code
 * it blocks third party developers from using the proper APIs to monitor
 usage

 Initially I think it would be better to investigate back-off in the
 Gutenberg repo and monitor how that goes before messing with caching
 algorithms

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