[m_b]

Please, Synapse isn’t production ready, at all. See this issue for example: https://github.com/matrix-org/synapse/issues/3364, reported back in 2018, labelled highest priority since then and still not fixed. This is indeed a huge problem, because if you don’t have shit tons of money to put in your database server’s storage you’ll quickly get stuck. Some workarounds mentioned are non-safe hacks and shouldn’t be necessary for a production ready messaging server.

[Arathorn]

This bug is not generally a significant cause of disk space utilisation, unless you’re running a server the size of matrix.org (which is the only reason it’s marked P1).

I strongly suspect you’re thinking of a separate issue: the need to automatically expire old history and reclaim disk space in general, which was fixed a while back, as per https://github.com/matrix-org/synapse/blob/master/docs/messa...

[omnimus]

Ive been running synapse for atlest 3 years for very active group of about 40 on tiny 1gig ram server and its been great. The main issue is if you start to federate with main matrix instance which is gigantic and can slow things down.

But i dont need to federate and use it more as Slack and it just keeps getting better.