• 17 Posts
  • 1.28K 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.












  • The kernels (and accompanying modules/drivers) are more or less freely interchangeable.

    Bugs in the kernel are pretty rare in my experience. I think it’s more likely that the bug was somewhere in KDE Plasma. Kubuntu’s version should be older than the one on Cachy. On top of that Kubuntu has their own patches for KDE, so even if the version numbers are the same they are not the exact same programs. And on top of that the way they compiled KDE will be slightly different.