[wp-trac] [WordPress Trac] #64696: Real time collboration effectively disables persistent post caches while anyone edits a post
WordPress Trac
noreply at wordpress.org
Thu Mar 19 15:03:48 UTC 2026
#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 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?
**Awareness write frequency**
@peterwilsoncc suggested bucketing awareness timestamps to 5-second
intervals so that most awareness polls skip the DB write entirely.
Combined with the existing short-circuit (skip UPDATE when `date_gmt`
hasn't changed), this would reduce awareness write volume by roughly 80%.
He also suggested a filter for allowing hosts to set awareness
granularity. Input from @czarate on how this affects the client experience
would be helpful.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:101>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list