fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-24 17:52:11 +00:00
Code Issues Projects Releases Wiki Activity

Clarification: a pg backend is coming to Conduit

Browse source
This commit is contained in:
Rohan Kumar 2022-11-15 12:26:14 -08:00
parent 0772848146
commit 2cebff0625
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/notes/matrix-performance-problems.md
View file

@ -11,6 +11,6 @@ Synapse is incredibly slow, which is why I run the [Conduit matrix server](https
This also gives Matrix a spam DDoS problem: sometimes people mass-create accounts on hundreds of servers with open registration, and mass-join rooms. The flood of thousands of join-events will <abbr title="Out Of Memory">OOM</abbr> most connected servers. My Conduit server (RocksDB backend, 1 vCPU, 1GB RAM) is actually fast and light enough to ride some of these out and go back to normal speeds a couple hours after the floods die down.
You generally don't want to join a room like Matrix-HQ unless you have good hardware. A new Postgres backend is coming soon, which should improve the situation.
You generally don't want to join a room like Matrix-HQ unless you have good hardware. A new Postgres backend is coming to Conduit soon, which should improve the situation.
Once Conduit implements a few missing features (federated backfill, spaces hierarchy and room discovery), and once better spam controls roll out (e.g. automatically restricting joins to under <var>N</var> per second and/or automatically blocking open-registration servers during high join frequencies), I'd say the worst performance problems will be gone.