Server resources are not that high because of the protocol, but because it’s done in fucking Python, which is inherently inefficient.
Yes in any other language it will still need more resources than IRC, but not that amount as now, and I think the tradeoffs are worth it.
An other thing is the resource usage of the clients.
Well yes if nearly all of the clients are made in web garbage then it’s no surprise they’ll be resource hungry.
But an other point that worsens the situation is that currently synchronization is done in a way that practically requires clients to keep all your joined rooms in memory. Change is on the way, fortunately, though.
That’s why I’m glad Lemmy is written in Rust. I know that the instance admins are getting the most bang for their buck when they aren’t wasting CPU cycles on running an interpreter.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Server resources are not that high because of the protocol, but because it’s done in fucking Python, which is inherently inefficient.
Yes in any other language it will still need more resources than IRC, but not that amount as now, and I think the tradeoffs are worth it.
An other thing is the resource usage of the clients.
Well yes if nearly all of the clients are made in web garbage then it’s no surprise they’ll be resource hungry.
But an other point that worsens the situation is that currently synchronization is done in a way that practically requires clients to keep all your joined rooms in memory. Change is on the way, fortunately, though.
That’s why I’m glad Lemmy is written in Rust. I know that the instance admins are getting the most bang for their buck when they aren’t wasting CPU cycles on running an interpreter.
Sounds like a hard pass until these are resolved.