This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Improve time to join a remote room #14030
Labels
A-Federated-Join
joins over federation generally suck
O-Frequent
Affects or can be seen by most users regularly or impacts most users' first experience
S-Major
Major functionality / product severely impaired, no satisfactory workaround.
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Z-Epic
Users expect joining a remote room to be fast - a few seconds at most.
The current work being undertaken is protocol level work to allow you to "partially" join a remote room, which allows you to send and receive events, while the join fully completes in the background. End of Q3 we put it out for community testing, with the caveats it a) has lots of edge cases and bugs, and b) doesn't work for worker deployments.
The backend team are currently estimating the remaining work before it can be enabled by default across all deployments.
Note: there is a separate (smaller) tranche of work to actually optimise the code involved in the presence of faster remote room joins. So once the above is complete there might still be a bunch of work to do to get it to a few seconds at most.
Relevant milestones:
These tasks need to be completed for this issue to be closed:
_sync_partial_state_room
clears the partial state flag for a room #13173lazy_load_members
/sync
s should not block #12989heroes
to handle nameless rooms #12995TestPartialStateJoin/Resync_completes_even_when_events_arrive_before_their_prev_events
is flaky #13777TestPartialStateJoin/Rejects_send_knock_during_partial_join
is flakey(?) #13945TestPartialStateJoin/*
due to complement hostname:port re-use #13975The text was updated successfully, but these errors were encountered: