This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Receipts worker needs to be sharded #16417
Labels
A-Workers
Problems related to running Synapse in Worker Mode (or replication)
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Major
Major functionality / product severely impaired, no satisfactory workaround.
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Currently we can only run one receipts worker, we should be able to shard this.
Annoyingly, it looks like most of the CPU cost for receipts is just "overhead", i.e. receiving HTTP requests, DB pool, and replication overhead.
A representative flame.svg:
The text was updated successfully, but these errors were encountered: