

Looks like it since it came from fedia. I would need to take a peek at the AP json to be sure when I get a chance. The picture and the link come as two attachments, and PieFed just pulls the first one, the picture.
Piefed contributor and part of the piefed.social admin team.


Looks like it since it came from fedia. I would need to take a peek at the AP json to be sure when I get a chance. The picture and the link come as two attachments, and PieFed just pulls the first one, the picture.


I run a personal lemmy instance and two personal piefed instances, so I was just doing some comparisons. My instances are mainly used for development and testing, so they are only subscribed to a handful of communities and just have one active user.
You are correct that when it comes to performance, like snappiness and responsiveness, the database is probably going to be the bottleneck. Unless you are scaling up to a huge degree, I would be surprised to see meaningful differences in the number of requests that could be handled due to language differences between rust and python. Yes, python is an interpreted language, but most of the libraries you are using are basically calling other system libraries written in a language like C, and the program can execute way faster than your database I/O can give it data to process anyway.
Here is my usage summary. The lemmy instance has been running for about 1.5 years while the piefed instance has been running for just shy of a year now. I have only included the memory usage and disk since I don’t think either is really CPU hungry or bound in my use case.
| Software | Memory consumption | Disk Usage |
|---|---|---|
| Lemmy | ~1.5 GB | ~800 MB |
| Piefed | ~1 GB | ~200 MB |
Mbin 1.9 just came out and lets users basically set a custom image to go with the link. However, the way it federates is kind of messing up lemmy and piefed, where they just think it is a link to the image only.