element-hq / element-hq/synapse
Performance problems with bridges with ephemeral events enabled
Open
A-Application-Service
S-Minor
T-Defect
Z-Help-Wanted
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 600
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 51
Description
This issue has been migrated from [#8903](https://github.com/matrix-org/synapse/issues/8903).
---
A lot of these problems seem to happen at scale. This is what we saw when we restarted matrix.org with ephemeral events enabled for the OFTC bridge:
- The memory usage of the appservice worker has increased ~3.5x, presumably to handle caching of members in rooms ahead of time.
- CPU will churn during startup handling `notify_interested_services_ephemeral`
- The database will be hammered for `get_users_in_room` and `set_type_stream_id_for_appservice`
Contributor guide
Assessment
This issue has not been assessed yet.