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

 Replying to [comment:101 JoeFusco]:
 > Two open architecture questions from [https://github.com/WordPress
 /wordpress-develop/pull/11256 PR #11256] that would benefit from input
 here.
 >
 > **Index coverage for the polling query**
 >
 > @czarate noted on the PR that the polling query filters on type !=
 'awareness':
 >
 > {{{
 > #!sql
 > SELECT data FROM wp_collaboration WHERE room = %s AND type !=
 'awareness' AND id > %d AND id <= %d ORDER BY id ASC
 > }}}
 >
 > The current KEY room (room, id) doesn't cover the type filter. A
 composite KEY (room, type, id) would let MySQL satisfy the query entirely
 from the index. @pkevan agreed this seems sensible given the queries.
 @peterwilsoncc, thoughts on whether this is worth adding now or deferring?


 Yes, this is why I asked about a covering index above.

 > I am wondering if a covering index for KEY room_type_id(room,type,id)
 would be tighter for polling since there might be queries that either
 include/exclude event types?

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