this post was submitted on 01 Jul 2023
3683 points (97.1% liked)

Lemmy.World Announcements

29156 readers
348 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 info@lemmy.world e-mail.

Report contact

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

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

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 @stanford@discuss.as200950.com and @sunaurus@lemm.ee 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 @sunaurus@lemm.ee 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
[โ€“] blueoak@lemmy.world 18 points 2 years ago (3 children)

I'm not sure if this has been said but, when I open lemmy on browser, my account would sometimes be someone elses. I don't know if it's a bug and I saw it happen three times to me so far, and it even happened again a few minutes ago. It's like I i logged into someone elses account, I saw three other usernames so far. A few minutes ago it said my account was Professor -?-?-?- with that account's profile picture shown too. It only does that for half a second before it returns back to my account.

I'm just making sure this is said because I don't want to one day accidentally log into someone else's account by accident.

[โ€“] SouthernCross@lemmy.world 7 points 2 years ago

Ok that's bizarre.

[โ€“] blueoak@lemmy.world 6 points 2 years ago* (last edited 2 years ago) (2 children)

edit: https://imgur.com/a/I4rO1pV here is the bug that I was talking about. and i dont think i should say why it happens either.

[โ€“] ItsDedo@lemmy.world 6 points 2 years ago

Definitely a caching issue. @Ruud does the nginx instance also do caching? Maybe you can restrict it to non-logged-in requests

[โ€“] ItsDedo@lemmy.world 3 points 2 years ago

Definitely a caching issue. @Ruud does the nginx instance also do caching? Maybe you can restrict it to non-logged-in requests

[โ€“] Nano@lemmy.world 3 points 2 years ago