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

Receipts worker needs to be sharded #16417

Closed
#16432
Closed
Receipts worker needs to be sharded#16417
#16432
Labels
A-WorkersProblems related to running Synapse in Worker Mode (or replication)O-UncommonMost users are unlikely to come across this or unexpected workflowS-MajorMajor functionality / product severely impaired, no satisfactory workaround.T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
@erikjohnston

Description

@erikjohnston
erikjohnston
opened on Oct 2, 2023

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:

flame

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-WorkersProblems related to running Synapse in Worker Mode (or replication)O-UncommonMost users are unlikely to come across this or unexpected workflowS-MajorMajor functionality / product severely impaired, no satisfactory workaround.T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions