Lemmy.World Announcements

28381 readers

1 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email [email protected] (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 2 years ago

MODERATORS

[email protected]

3478

Lemmy.world updated to 0.18.1-rc (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

574 comments fedilink hide all child comments

Looks like it works.

Edit still see some performance issues. Needs more troubleshooting

Update: Registrations re-opened We encountered a bug where people could not log in, see https://github.com/LemmyNet/lemmy/issues/3422#issuecomment-1616112264 . As a workaround we opened registrations.

Thanks

First of all, I would like to thank the Lemmy.world team and the 2 admins of other servers @[email protected] and @[email protected] for their help! We did some thorough troubleshooting to get this working!

The upgrade

The upgrade itself isn't too hard. Create a backup, and then change the image names in the docker-compose.yml and restart.

But, like the first 2 tries, after a few minutes the site started getting slow until it stopped responding. Then the troubleshooting started.

The solutions

What I had noticed previously, is that the lemmy container could reach around 1500% CPU usage, above that the site got slow. Which is weird, because the server has 64 threads, so 6400% should be the max. So we tried what @[email protected] had suggested before: we created extra lemmy containers to spread the load. (And extra lemmy-ui containers). And used nginx to load balance between them.

Et voilà. That seems to work.

Also, as suggested by him, we start the lemmy containers with the scheduler disabled, and have 1 extra lemmy running with the scheduler enabled, unused for other stuff.

There will be room for improvement, and probably new bugs, but we're very happy lemmy.world is now at 0.18.1-rc. This fixes a lot of bugs.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

I had the same problem on lemm.ee when that admin upgraded it. In my case, it only happened when I was on Firefox on the desktop. It happened because I had Spanish installed as a display language.

If you have more languages than just English installed in the browser, remove them, close the browser, re-open the browser and see if it works. @https://lemmy.world/u/ruud, If you see this, ask @https://lemm.ee/u/sunaurus what he did to fix the issue on the backend.

I did a write-up on what I tried. My username is the same on lemmy.world as it is on lemm.ee.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Thanks! That was it. I'm using Firefox on Android. Changed language to English (US) and it worked! @[email protected] can you please check this issue? using a browser with a default language other than English will result in the page not loading correctly. Workaround is just setting the browser language to English. Thanks!