Lemmy is booming

I have never before received so many reactions and comments on my Lemmy posts before, so it’s obvious to see, that there are many new members here.
Welcome to all the new! And I’m looking forward to see more of you here.
Cheers!

  • tmpod
    8•1 year ago

    I have been running a (unfortunately still low local volume) instance with a big federation pool for a while now, and resources are really manageable. CPU usage is almost non-existent (save for a few short spikes), pretty much always below 5% of my ~2GHz vCPU. RAM has never gone above 500MB, and typically sits around 250MB (mostly from postgres). Network I/O has never surpassed 50MB combined daily. Disk I/O is slightly higher, averaging at 40MB combined daily.

    Overall, it’s really cheap to get a Lemmy instance up and running for you and some friends, and with the officially provided Ansible setup (and I believe there’s a Yunohost package as well), getting one operational is pretty easy.

    • KNova
      1•1 year ago

      The yunohost package is broken and outdated unfortunately. It’s a version behind and it doesnt support image uploading (for users submitting content OR for admins adding a server logo).

      I have never used Ansible before yesterday, and I figured it out in about 15 minutes using the official Lemmy documentation. I’d encourage anyone reading this who is considering administering an instance to skip the Yunohost package for Lemmy at this time.

      • tmpod
        1•1 year ago

        Oh, that’s a pity :(
        Someone should take the lead there then. But yeah, Ansible is pretty great! I rock my own setup because I feel more comfortable this way, but it was originally based on the first Ansible setup hehe

        • KNova
          1•1 year ago

          I don’t want it to seem like I am talking down on the “Lemmy for Yunohost” package maintainers. They are doing a job I could not do, and for zero compensation. It’s just unfortunately not receiving the attention it needs for production purposes, IMO

          • tmpod
            1•1 year ago

            I did not read it like that either! Perhaps I misworded. I meant that, since last update seems to have been on September 25th 2022, the maintainer probably is too busy right now, and if someone else feels they could help out, they should :)