Right now, im using a single instance lemmy on my own servers. I have a couple of issues with it that im not quite sure what to do with:
- It seems to make a LOT of calls to other servers. Its almost constantly pinging other servers asking for updates.
- It gets de-federated almost instantly from popular instances. Which kinda sucks.
- It uses up quite a bit of CPU compared to other federated applications.
- Subscribing to instances seems to work most of the time, but sometimes it just errors out and I have to re-do it.
Im pretty sure if I update my version to the newest version of lemmy I may get around 2/4 but even when I used a fairly new dockerized version of lemmy, it seemed like it was calling a LOT of servers/using a lot of CPU for something I would like to have it update maybe once an hour or so.
Essentially im looking for something like GoToSocial is to Mastodon but for lemmy. Hope that makes sense.
Is there anything like that out there? Piefed maybe?
Some people report less server load with Piefed.
Yeah I need to take another look at piefed. Thanks for the read.
But man the best part is the resources it consumes. Let me remind you that Lemmy puts a load of 12 on the server, when I turn off Lemmy the load with the other 13 web services running on the server is 0.5 and when I turn on PieFed the load is 1.
Im also looking for the same thing.
threaded-discussion server products require far more resources than a simple mastodon, twitter like server. if you want to federate with the threadiverse its going to be resource intensive.
Why is this the case?
twitter/mastodon is just an old man shouting into the cloud (single to many). the discussion is very limited in scope. forums (many to many) are much more intensive due to the volume of human activity and its nested interactions with said data.
even if you just look at the biggest players thats dozens of servers with 100k users all upvoting/replying/moderating and your instance needs to process that if you want a decent interaction.
First link at least is wildly over-claiming the difference. The data they describe is all cached in the browser and occurs once. PieFed uses ActivityPub, so network differences are moot since the same data transfers.
- It seems to make a LOT of calls to other servers. Its almost constantly pinging other servers asking for updates.
The fediverse works the other way around: other instances push activities to yours. If you have a lot of subcriptions to large communities like !technology@lemmy.world it will indeed receive a lot of activities.
- It gets de-federated almost instantly from popular instances. Which kinda sucks.
Mine’s not been defederated from anywhere, not even Beehaw
- It uses up quite a bit of CPU compared to other federated applications.
It definitely uses a fair bit of CPU but it is ingesting a fair amount of data, but still not a ton either:
Although I do hear PieFed is a lot lighter.
- Subscribing to instances seems to work most of the time, but sometimes it just errors out and I have to re-do it.
That settled for me after a week or so of running mine. My subscriptions always go through.
What version are you running? Im currently running 0.18.2 (mostly because thats what yunohost supports).
Latest (0.19.8). 0.18 is very old, over a year old, later versions dealt with a lot of scaling/performance problems.
That sounds very typical of YunoHost to have wildly outdated software
Yeah it’s all community based. And like Debian super stable. But the issue with that is updates take a very long time.