A chat server running on powerful hardware collapsing when handling more than 100 events per second isn't acceptable. Events scale up based on room activity from non-local users including spammers too. It's an issue for a server with 12 users too.
https://element.io/blog/scaling-to-millions-of-users-requires-synapse-pro/
=> More informations about this toot | More toots from GrapheneOS@grapheneos.social
Choosing to write the Matrix server software in Python in the first place was a huge mistake. It's now far harder to develop and maintain the software. It heavily contributes to it being buggy and fragile. It's the biggest factor in it being so incredibly slow and hard to scale.
=> More informations about this toot | More toots from GrapheneOS@grapheneos.social
@GrapheneOS slightly simplistic view… it’s very possible to write python that doesn’t suck (though it wouldn’t be my first choice for this; Rust or something Erlang-ish probably). But from an outside perspective it sure sounds like they are intentionally handicapping the design of the open source product.
=> More informations about this toot | More toots from ianthetechie@fosstodon.org
@ianthetechie They got 500x performance with a partial in-place rewrite in Rust using the same architecture, database structure / connections, algorithms, data structures, etc. It's an in-place partial rewrite and all that's really changing is the language. They put huge effort into trying to optimize the Python and make it work that way. It is not capable of providing reasonable performance for this. It's also clearly far less maintainable at this level of complexity and scale.
=> More informations about this toot | More toots from GrapheneOS@grapheneos.social
text/gemini
This content has been proxied by September (3851b).