this post was submitted on 01 Jul 2023

3749 points (97.3% liked)

Lemmy.World Announcements

29218 readers

15 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]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

3749

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

submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

567 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.

(page 10) 50 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 2 years ago

Let's gooo

[–] [email protected] 1 points 2 years ago

Thank you! Your hard work is truly appreciated.

This whole upgrade process reminded me to check the patreon donation stuff for y'all.

[–] [email protected] 1 points 2 years ago

So I can't login and the reset passwork button doesnt seem to do anything 💀

[–] [email protected] 1 points 2 years ago

Thank you!

[–] [email protected] 1 points 2 years ago

Nice, hopefully this'll fix the auto refreshing new posts on PC! Thanks man ^^

[–] [email protected] 1 points 2 years ago

Thanks very much for your time and effort Ruud, it's much appreciated! Now, after you've put the kids to bed, grab yourself a beer and put your feet up!

[–] [email protected] 1 points 2 years ago

@ruud Thank you! This is an important one for the community! And maybe the servers too. ;)

[–] [email protected] 1 points 2 years ago

Congrats on figuring it out! I'm just wading into docker in a professional capacity so I admit some of it feels like magic to my traditional developer brain but glad it worked out.

[–] [email protected] 1 points 2 years ago

good job

[–] [email protected] 1 points 2 years ago

Tried to comment "looking good" but can't seem to comment. Getting a timeout.

[–] [email protected] 1 points 2 years ago

Cool beans, WefWef also seems to work now again :)

[–] [email protected] 1 points 2 years ago

Thank you for your hard work getting this working. It's much appreciated :)

[–] [email protected] 1 points 2 years ago (2 children)

Question @[email protected] why update to the release candidate? Just want to help testing? Or was there some readdition (ie: captcha) that had you quick on the trigger?

load more comments (2 replies)

[–] [email protected] 1 points 2 years ago

Good job! 🎉🎉

[–] [email protected] 1 points 2 years ago

I'm a reddit migration and love what I saw so far! Keep it up!

[–] [email protected] 1 points 2 years ago

Clearing the cache seems to have fixed the login bug.

There is another big going on where I'm seemingly logged out all the time though.

[–] [email protected] 1 points 2 years ago

Congratulations on getting it up and running!

[–] [email protected] 1 points 2 years ago

🎉

[–] [email protected] 1 points 2 years ago

Bug I’m running into -

When my mobile browser (Firefox, iOS) language is set to something other than English, not content loads and I am unable to log in.

[–] [email protected] 1 points 2 years ago

Thank you so much for doing this! The having an instance this big really made the difference for leaving reddit. I really missed jerboa and am glad to have it back as a client.

[–] [email protected] 1 points 2 years ago

Thank you so much for doing this! The having an instance this big really made the difference for leaving reddit. I really missed jerboa and am glad to have it back as a client.

[–] [email protected] 1 points 2 years ago

Thank you for all your hard work running this instance and for keeping us posted!

[–] [email protected] 1 points 2 years ago

On a somewhat related note, how are you coping with the scaling from the Reddit migration?

load more comments