Given, I have a small blog (ie low load on cactus), but I'm in many (15+) medium sized (100-1000 members) federated chats and it's just fine on a day to day basis.
There are some limitations tho:
- I can't join large rooms (2000+ members and whatever number of servers that entails on average)
- Initial sync (first time log in on new client) is crazy slow - syncv3 will hopefully fix this
My definition of not being resource hungry is being able to run on a 1gb, 1 vCPU VM - however you and me might have a difference in that opinion
My instance of Synapse definitely can't join any matrix.org chatrooms, no matter how hard I try. Even rooms with a few hundred participants are awfully slow and leave scrollback state a broken mess. When I tried to join the main Matrix channel, both of the CPU cores I had dedicated to Synapse were pinned for at least half an hour, even after I tried to cancel joining the room!
I hope sync v3 lives up to the hype, but I'm wary. Synapse's Pythonic base seems ill-fitted for an instant messenger backend in my opinion, and no amount of protocol trickery can work around that.
It's not that I think the 1GiB is necessarily that excessive, but Dendrite and Conduit are blowing Synapse out of the park in terms of performance, to the point that I'd almost rather see the Matrix folks dedicate their development efforts more on bringing Dendrite up to speed than to expanding functionality.
The main thing that bogs down Synapse is if users join massive federated rooms and you end up replicating huge amounts of traffic onto your server. So we’re working on that too via Fast Joins and better-than-full-mesh federation for P2P.
I once installed Litecoin Core (on Windows 10) on my desktop PC. I had Comcast (branded as Xfinity) broadband, whatever speeds my region and apartment supported. I had a 1TB monthly limit before throttling. I lived in the east SF bay area. I downloaded Litecoin Core software at the beginning of the month. I got dial-up speeds for the rest of the month. I got a 5x average bill that I had to negotiate down. Nobody on my server even cared about the federated rooms, it was just me trying to give them more flexibility.
Allowing federation with Matrix has the same issue, and I know it's being addressed, but I want to hammer this home. Self hosting means normal, poor people, too, not just EU government entities and Upcoming Big Tech partners. I know you know this, but every advocate needs reminders here and there.
The initial sync issue is only a problem for large accounts which have joined many rooms. Cactus comments creates a guest user for non-logged-in commenters, and an empty guest account is pretty much instant to load in my experience.
You can go to my cactus comments instance (running on aforementioned 1gb machine) to test out the speed https://karmanyaah.malhotra.cc/tech/2021/06/website-things/
In my opinion, the biggest problem with the current Matrix platform, especially if you self-host, is the server implementation. It's not buggy, but it's just awfully slow. The "dpt of ping" [2] section at the bottom of the weekly Matrix updates show that five seconds of latency between servers (measured by basic ping bots) is far from uncommon. The latency is still significant in the non-synapse version of the graph, but it's much better already.
With the speed new MSCs are accepted every month I don't think any alternative server stands a chance at catching up to Synapse any time soon, and I don't know how I feel about that. Yes, Matrix is an open platform with an open source spec, but it's effectively impossible to develop an alternative backend implementation with the way development is currently done, unless you've got a lot of developers and money to throw at the platform.
I'll probably look into Conduit again in a few months, hopefully the project will keep up it's impressive pace so that it's useful for my purposes.
[1]: https://cactus.chat/
[2]: https://matrix.org/blog/2021/12/17/this-week-in-matrix-2021-...