element-hq / element-hq/synapse

massive storm of presence EDUs when joining a large room

Open
#3,120 0 comments 0 reactions 0 assignees View on GitHub
A-Federated-Join A-Join A-Performance A-Presence O-Frequent S-Major T-Defect
Dominant language
Python
Stars
4.6k
Forks
600
Avg merge
5d 22h
Merged PRs (30d)
51

Description

This issue has been migrated from [#3120](https://github.com/matrix-org/synapse/issues/3120).

---

after you do your send_join to a room, all the servers in the room seem to immediately send you presence updates. Since this will often be the first contact you get from those servers, we then end up doing hundreds of server key requests, all of which end up starving out the actual join request - contribuiting to the join itself taking ages.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the send_join flow and the handling of incoming presence updates and server key requests. Determine how these requests compete with the join request, then verify that joining a large room no longer produces a storm of key requests that delays completion.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
distributed-systems, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.