From 2cebff06250dc6abdad1276ebf495286e2bf5155 Mon Sep 17 00:00:00 2001 From: Rohan Kumar Date: Tue, 15 Nov 2022 12:26:14 -0800 Subject: [PATCH] Clarification: a pg backend is coming to Conduit --- content/notes/matrix-performance-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/notes/matrix-performance-problems.md b/content/notes/matrix-performance-problems.md index 4ac5dd1..5ece8c3 100644 --- a/content/notes/matrix-performance-problems.md +++ b/content/notes/matrix-performance-problems.md @@ -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 OOM 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 N per second and/or automatically blocking open-registration servers during high join frequencies), I'd say the worst performance problems will be gone.