this post was submitted on 01 Jul 2023
3985 points (97.9% liked)

Lemmy.World Announcements

29156 readers
5 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

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
ruud
lwadmin
lwCET
jelloeater85
Serinus
lw_mod_notification
3985
Lemmy.world updated to 0.18.1-rc (self.lemmyworld)
submitted 2 years ago* (last edited 1 year ago) by ruud to c/lemmyworld
480 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
[โ€“] Tag365 19 points 1 year ago (5 children)

I had a strange bug today where I wasn't able to upvote comments. So I cleared out my website data like the website suggested and I started having problems logging in. It would log in but then when I refreshed it wasn't logged in anymore. It stopped after a while but then when I clicked on an old tab when I refreshed I was logged out again. So, the log in issue must be something to do with how iOS Safari handles web cache on tabs.

[โ€“] normalmighty 8 points 1 year ago* (last edited 1 year ago)

Upvotes aren't responding for me, but the comment is marked as upvoted when I refresh the page. I think it just isn't rerendering on the frontend.

Edit: same thing is happening when posting comments. I refresh and the comment was posted, but without refreshing it's marked as loading forever.

[โ€“] Patrizsche 5 points 1 year ago

Exactly same thing for me (but on Chrome on Windows), I emptied my cache and I just can't log in (says it worked, but it really doesn't)

[โ€“] feitingen 5 points 1 year ago

I had the same issue with Firefox on Linux. I had to clear website data again to fix it.

I had the F12-mode open to see what was going on with cache disabled, so that might have helped as well.

[โ€“] Tag365 2 points 1 year ago (1 children)

I suddenly got "logged out" again, but when I opened a new tab and went to Lemmy.world I was still logged in.