• 4 Posts
  • 292 Comments
Joined 3 years ago
cake
Cake day: July 8th, 2023

help-circle



  • I was and still am on HDD. The CPU was upgraded as well. I migrated to a new server.

    The main culprit was the database. As far as I’m aware Lemmy is missing some indexes and due to the ORM they used didn’t always have optimised queries. Now with 64 GB RAM the whole database (almost 30 GB) fits in there fixing most of those issues.

    The real fix will probably come with Lemmy 1.0. They radically changed the database layout and queries.

    Image proxying wasn’t bad for performance. Just storage space. It was growing really really fast. Now that only I am using it to host the pictures I uploaded it is still much too large (24 GB). But its directory structure is so convoluted that I can’t really debug it. My stuff really shouldn’t be taking up more than a few hundred MBs.

    I am the only one using this instance. I am subscribed to a hundred communities or so. I am always pretty up to date with my Lemmy versions.





  • I run an instance just for myself and it was a nightmare on HDD and 16 GB RAM. It was slow as molasses. Supposedly the database layout will be fixed with the 1.0 release that is just around the corner.

    Since I upgraded to 64 GB it’s been pretty smooth. Still wild that that is necessary for a single user.

    Also, disable image proxying. I have no idea what pict-rs does but it seems to be too much.

    You should consider running Piefed instead. It’s not as resource hungry as Lemmy.




  • More or less.

    • Zswap is better than zram because it’s integrated with the kernel. Swap in zram is more of a hack.
    • zram can kill your file cache unnecessarily, which leads to more disk reads.
    • Don’t use zram without an oom killer.
    • They’re working on zswap to not require any disk swap at all, basically killing the last reason why one might want to use zram over zswap.


  • That’s the way it goes with the scale from simple to “something that fits our needs”. Either something is too simple or it is so complex that you can’t let your more challenged users at it. So you end up rolling your own solution.

    That’s how many companies end up with monstrous Excel or Access applications.

    The upside of having your own app that uses common open source components is that integration with other tools is easier later down the line. Make it web based and it can run on basically every computer on the planet. Use PostgreSQL or MySQL in the backend and you can easily add other frontends if needed.