Regression in federation sender instance calls to get joined profile
See original GitHub issuev1.61.1 release dramatically reduced federation sender calls to the _get_joined_profile_from_event_id
cache (see: https://github.com/matrix-org/synapse/pull/12955#issuecomment-1162800438). This seems to have returned in 1.63.1, the jump below is when we upgraded from 1.61.1 -> 1.63.1:

Issue Analytics
- State:
- Created a year ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
`user_directory.notify_new_event` throws exception whenever ...
Found while running the MSC2716 Complement test suite (COMPLEMENT_ALWAYS_PRINT_SERVER_LOGS=1 COMPLEMENT_DIR=../complement .
Read more >CHANGES.md · 2d295a4be92894d18d71512548db8629a3ed4b50 ...
This release fixes a regression in Synapse 1.32.0 that caused connected Prometheus instances to become unstable. However, as this release is still subject ......
Read more >Federated Identity Management and Web Services Security
advantage of identity federation to improve customer experiences, reduce costs, and improve overall security. This scenario, for example, involves two large.
Read more >CMDB Federation Specification (DSP 0252) - DMTF
The federated CMDB described in this specification is a collection of services and data repositories that contain configuration and other data ...
Read more >Category: Releases | Matrix.org
Today we have released Synapse 1.21.2, which fixes a couple of minor bugs that ... Improved federation sender logic (resend retries, backoffs, blacklisting, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
sorry, missed this.
matrix.org
apparently has 20 federation senders, handling a total of around 100 outgoing federation PDUs per second. But note that the code that hitsget_joined_hosts
is done before the work is sharded (ie, each of the federation senders does the lookup for every event).Possibly…
Is it possible that we now avoid pulling all of the state out of the database during the event-creation path… right up until we attempt to
cache_joined_hosts_for_event
, when we’ll suddenly need to pull the entire membership list out of the database?