-
Notifications
You must be signed in to change notification settings - Fork 568
Throttle sync-driven presence updates relayed to the presence writer #19941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
60328ea
Throttle sync-driven presence updates relayed to the presence writer
erikjohnston f2da818
Newsfile
erikjohnston a704b5c
Update synapse/handlers/presence.py
erikjohnston dba4365
Ensure _user_devices_going_offline doesn't get added to if presence i…
erikjohnston 5037199
Fixup
erikjohnston 38a0bfd
Fixup2
erikjohnston 4a5d854
Merge branch 'develop' into erikj/presence-throttle-sync-set-state
erikjohnston 7de8ba8
Derive the presence relay throttle interval from the configurable timers
erikjohnston File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Reduce replication traffic caused by presence. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we possibly also listen from presence updates from other workers assuming that goes through the notifier? so that we don't rely too much on worker stickiness for this to be effective
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Annoyingly not easily in the current design, as the
set_state(which is what we're throttling) is a HTTP API that keeps things alive on the presence worker (without it going down replication streams).Ideally we'd actually avoid doing periodic
set_stateand merge it's semantics intoUSER_SYNCreplication command that we're already sending, to remove a lot of the HTTP API chatter for presence. Have set off claude to look into that, but it sounds like a more involved change.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got something working at #19946, though it's a much chunkier change so I'd be tempted to land this first, and then land the bigger PR at a slower pace.