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

help-circle

  • After some amount of pain with sushi belts, I’ve just stolen the design from Nilaus with passthrough filtering splitters and bots, so very much similar to your setup but two main belts.

    https://youtu.be/qr_Lep5UCJU?t=37m2s

    Not at pc so don’t have a BP but basically like this:

    The outter belt is the overflow that goes through an array of speed boosted recyclers and the output goes back to the inner main as priority input.
    You do have to account for the secondary outputs of the recycled overflow, so green circs, iron and copper plates, iron ore etc

    Edit: the item filter of the storage chests must match the filter of the respective splitters (obviously), like this bots will prioritize these chests for both requests and “storage”. Edit2: it is ready for quality upcycling but we didn’t have time/felt like it at the moment


















  • 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.