• 7 Posts
  • 85 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle







  • Numbers from my instance, running for about a 1 year and with average ~2 MAU. According to some quick db queries there is currently 580 actively subscribed communities (it was probably a lot less before I used the subscribe bot to populate the All tab).

    SELECT pg_size_pretty( pg_database_size('lemmy') ): 17 GB

    Backblaze B2 (S3) reports average 22.5 GB stored. With everything capped to max 1 USD, I pay cents - no idea how backblaze does it but it’s really super cheap, except for some specific transactions done on the bucket afaik, which pictrs does not seem to do.

    According to my zabbix monitoring, two months ago (I don’t keep longer stats) the DB had only about 14G of data, so with this much communities I am getting about 1.5G per month (it’s probably a bit more as I was recently prunning stuff from some dead instances).

    Prometheus says whole lemmy service (I use traefik) is getting within about 5 req/s (1m average) though if I go lower it does spike a lot, up to 12 requests within a second then nothing for few.









  • … certain parties violating the old license, by not attributing and stripping my copyright. Packagers being collateral damage was a beneficial side-effect, considering they don’t clearly mark their versions as modified (also a GPL requirement), break functionality, and expect upstream to provide support.

    Emphasis mine, snipped from the authors comment

    As a maintainer of few AUR packages this is always so hurtful.
    Where does this position come from? Packaging is the avenue that people using any linux distro use to get your software. This also my first time hearing that packages (re)building GPL code have to mark the packages as modified in some way. I can understand that being a valid concern (if it is one) but that’s a problem that can be rather easily fixed without throwing all of the maintainers overboard (?).

    I can see there being bad maintainers that will come shouting to upstream with every little thing that does not work on their platform, but man that’s just insincere towards maintainers that will dive, analyze and help where they can to make it work.
    For every one maintainer coming to your github issues with their problems there is probably shitton of patches and time spent on making your program work with the given distro.







  • How did you install jellyfin?

    It should not core-dump (read: hard crash, something has gone terribly wrong), at best you should get a configuration error and errors like that.

    You can see the logs of any systemd service/unit with this: journalctl -u <name of sevice> so in this case journalctl -u jellyfin (Tip: add -f to follow the output of a running service - useful for monitoring).

    Note that some programs log to their own files (and not to stdout) so if the above command comes out empty you should look into /var/log/ directory.