Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Shard event persister #7986

Closed
erikjohnston opened this issue Jul 30, 2020 · 0 comments
Closed

Shard event persister #7986

erikjohnston opened this issue Jul 30, 2020 · 0 comments
Assignees
@erikjohnston
Labels
A-Performance Performance, both client-facing and admin-facing A-Workers Problems related to running Synapse in Worker Mode (or replication)

Comments

@erikjohnston
Copy link
Member

We should figure out how to shard the event persisters, which means sharding the event stream and appropriately encoding that in e.g. sync tokens.
@erikjohnston erikjohnston added A-Performance Performance, both client-facing and admin-facing operation gemini labels Jul 30, 2020
@erikjohnston erikjohnston self-assigned this Jul 30, 2020
@clokep clokep mentioned this issue Sep 2, 2020
Merged
@erikjohnston erikjohnston mentioned this issue Sep 4, 2020
Merged
@richvdh richvdh added the A-Workers Problems related to running Synapse in Worker Mode (or replication) label Feb 16, 2022
This was referenced Apr 5, 2022
Merged
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@erikjohnston erikjohnston

Labels
A-Performance Performance, both client-facing and admin-facing A-Workers Problems related to running Synapse in Worker Mode (or replication)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richvdh @erikjohnston