perf: msc3902 partial joins and memoization for total joins #1537

Closed
gamesguru wants to merge 1 commit from gamesguru/continuwuity:guru/feat/impl/msc3902-partial-joins-and-caching-optimizations into main
Contributor

I advise no one test this out yet. Just something I scrapped together on my lunch break in response to #1503.
Likely needs further work.


commit msg log:

perf: msc3902 partial joins and memoization for total joins
impl partial join worker. batch server discovery and PDU queries
enable complement partial join tests

memoize full join auth chains (very basic moka LRU impl)

unit tests; refactor server query func for testability
enable `fast_joins=true` by default in config

fix lint with `url_preview` feature. TODO: suggest partial lints to avoid differential results.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
I advise no one test this out yet. Just something I scrapped together on my lunch break in response to #1503. Likely needs further work. ------------------------------------------------ **commit msg log:** ``` perf: msc3902 partial joins and memoization for total joins impl partial join worker. batch server discovery and PDU queries enable complement partial join tests memoize full join auth chains (very basic moka LRU impl) unit tests; refactor server query func for testability enable `fast_joins=true` by default in config fix lint with `url_preview` feature. TODO: suggest partial lints to avoid differential results. ``` **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [ ] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
perf: msc3902 partial joins and memoization for total joins
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled
443267ff74
I advise no one test this out yet. Just something I scrapped together on my lunch break in response to #1503.
Likely needs further work.

------------------------------------------------

**commit msg log:**

```
perf: msc3902 partial joins and memoization for total joins
impl partial join worker. batch server discovery and PDU queries
enable complement partial join tests

memoize full join auth chains (very basic moka LRU impl)

unit tests; refactor server query func for testability
enable `fast_joins=true` by default in config

fix lint with `url_preview` feature. TODO: suggest partial lints to avoid differential results.
```
Owner

I have said repeatedly we are not implementing partial join support as it leads to inconsistencies and a terrible user experience, especially when it (very commonly) goes wrong. I recommend instead working with the Matrix spec team to improve the spec for joins so that these problems are fixed at the source.

I have said repeatedly we are not implementing partial join support as it leads to inconsistencies and a terrible user experience, *especially* when it (very commonly) goes wrong. I recommend instead working with the Matrix spec team to improve the spec for joins so that these problems are fixed at the source.
nex closed this pull request 2026-03-13 11:45:29 +00:00
Author
Contributor

I think it leads to a terrible developer experience. Users are already affected by the ecosystem rot, as Synapse defaults to partial joins and so it's everywhere.

Regardless, there are some other basic speedups here for full joins.

I don't think implementing a ZK-SNARK msc proposal is going to happen any time soon, so doing a rigorous partial join implementation is probably the more reasonable short-term goal.

I think it leads to a terrible developer experience. Users are already affected by the ecosystem rot, as Synapse defaults to partial joins and so it's everywhere. Regardless, there are some other basic speedups here for full joins. I don't think implementing a ZK-SNARK msc proposal is going to happen any time soon, so doing a rigorous partial join implementation is probably the more reasonable short-term goal.
Owner

Synapse can reap what they sow, and recently have been doing so more and more often - I've had to patch out partial joins on my Synapse deployments because they're so horribly broken. There's no way you can make this resilient and reliable without looping back to square one and having joins as slow as non-partial joins. Genuinely, writing a proposal that doesn't involve using room inconsistency as an "optimisation" will be the faster route here.

Feel free to open another PR or re-push to this branch with just the other optimisations if you want, but MSC3902 support isn't going to be accepted due to aforementioned fundamental flaws.

Synapse can reap what they sow, and recently have been doing so more and more often - I've had to patch out partial joins on my Synapse deployments because they're so horribly broken. There's no way you can make this resilient and reliable without looping back to square one and having joins as slow as non-partial joins. Genuinely, writing a proposal that doesn't involve using room inconsistency as an "optimisation" will be the faster route here. Feel free to open another PR or re-push to this branch with just the other optimisations if you want, but MSC3902 support isn't going to be accepted due to aforementioned fundamental flaws.
Owner

Also for context - the only reason we support providing partial joins is because it's a bit of a bandwidth saver in the sense that it distributes the payload over multiple requests rather than uploading the entire state in one big response. We've got no incentive to support utilising them.

Also for context - the only reason we support *providing* partial joins is because it's a bit of a bandwidth saver in the sense that it distributes the payload over multiple requests rather than uploading the entire state in one big response. We've got no incentive to support utilising them.
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Required
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Required
Details
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1537
No description provided.