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

 Replying to [comment:90 griffbrad]:
 > With RC1 so close, we've had some more discussions about the custom DB
 table, and it just seems risky to introduce a schema change so late in the
 process. We do think there are likely benefits to having it in place
 ultimately, but the likelihood of getting the schema right without
 sufficient testing in production is low. Assuming Ella's patch is a viable
 approach to avoid the cache invalidation issue that inspired this issue
 originally, we'd like to take that route as it seems lower risk. Overall,
 our primary goal with RTC in 7.0 is to gather as much information as
 possible from hosts and plugin authors about how RTC affects the broader
 WP ecosystem. Once we have that information, we can more confidently add
 the custom table(s) that will make the feature the best it can be.

 Replying to [comment:110 griffbrad]:
 > Essentially, we did a review with Systems and talked over both options.
 This late in the game, they felt that the likelihood of getting the schema
 and performance characteristics of a new table right was more risky.
 You're totally right that WP_Query is a central API, but the patch was
 viewed as easy to reason about and easier to adjust if needed. Systems
 folks also felt the API in the patch was valuable outside the RTC context
 for other cases where post meta is written to in a way that too frequently
 causes cache invalidation, which they've seen from a variety of plugins in
 the ecosystem. Like I mentioned in this thread, I can definitely see the
 value in the custom table. I'd love to land it in 7.1. Both with the fixes
 to the cache invalidation issue and race condition from Ella and Chris,
 the post meta approach currently in use seems sufficient for the 7.0
 release.

 Please define to who you refer when speaking about "we", "folks" and
 "they".

 It's not helpful to have this kind of an comment nor possible to give any
 value for it, when "we", "folks" and "they" can be basically anyone from
 the streets.

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