this post was submitted on 01 Jul 2023
3756 points (97.2% liked)

Lemmy.World Announcements

29079 readers
244 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
 

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 3) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 1 year ago

πŸŽ‰ Great work!

[–] [email protected] 7 points 1 year ago

Loving lemmy more and more!

Just so refreshing getting this much transparency.

[–] [email protected] 7 points 1 year ago

I'm sure there will be bugs for others but it's smooth and bug free for me. Thanks so much for the devs and contributors.

[–] [email protected] 7 points 1 year ago

Just signed up and everythings working well for me!

[–] [email protected] 7 points 1 year ago

Hey, thanks for your hard work, just want to let you know that login doesn't work for me in incognito mode or on any app.

[–] [email protected] 7 points 1 year ago

Wow - we have a new defniition of 'awesome dudes'.

Thank you.

[–] [email protected] 7 points 1 year ago

YOU'RE DOING GOD'S WORK, SON! Keep up the good work! πŸ†

[–] [email protected] 7 points 1 year ago

Thank you from England for all the hard work AND for giving such interesting details, especially as it will encourage others to set up their own instances, and help them cross similar hurdles!!

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

Favicon seems to be missing now. Just a heads up! @[email protected]

[–] [email protected] 7 points 1 year ago

The instance just got so much more faster and stable, it's amazing. Keep up the good work!

[–] [email protected] 7 points 1 year ago

Awesome to see the transparency and some tech details of what these updates entail! I’m loving the bug fixes 0.18 brought too

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

I'm curious; is this instance pysically running on a local private server somewhere or in the cloud in some data center?

load more comments (3 replies)
[–] [email protected] 6 points 1 year ago (1 children)

Edit still see some performance issues. Needs more troubleshooting

Federation overheard is putting a lot of load on servers. Creating one task for every single post, comment, and vote in RAM-only queue.... pending changes: https://github.com/LemmyNet/lemmy/pull/3466

load more comments (1 replies)
[–] [email protected] 6 points 1 year ago

Lot of network errors, but it could be jerboa.

[–] [email protected] 6 points 1 year ago

Updated Jerboa. Thanks for your efforts, transparency and insights.

[–] [email protected] 6 points 1 year ago

Thanks for the hard work on the upgrade! Much appreciated although I'm only using the web version (not needing specific client apps). Lemmy World feels quite 'snappy' when browsing now.

[–] [email protected] 6 points 1 year ago

was struggling for a while, but it seem to be nice and fast now.. thank you!

[–] [email protected] 6 points 1 year ago

@ruud oh wow 0.18.1 fixed the broken federation/webfinger issue!!! this is great news

[–] [email protected] 6 points 1 year ago

we created extra lemmy containers to spread the load. (And extra lemmy-ui containers). And used nginx to load balance between them.

Had no idea nginx did that. There's so much I need to learn

[–] [email protected] 6 points 1 year ago

Lemmy seems pretty slow. I wonder how many more people have joined here now.

[–] [email protected] 6 points 1 year ago

Login problem is fixed for me, yay! Back on Jerboa and here on the browser! Thanks for your hard work and for putting up with me, lol.

I'm getting network errors that aren't allowing me to actually view content on Jerboa right now, though, but at this point I'm assuming it's a Jerboa thing and not a problem with the instance.

[–] [email protected] 6 points 1 year ago

Having login issues on the browser. Not logging in at all. But on liftoff where I was already logged in, everything seems to be working.

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

Have you considered running your Lemmy instance on more than a single machine? If it is possible to run two lemmy containers anyway (ie, lemmy is not a singleton), why not run them on separate machines? With load balancing you could achieve a more stable experience. It might be cheaper to have many mediocre machines rather than a single powerful one too, as well as more sustainable long-term (vertical vs horizontal scaling).

The downside would be that the set-up would be less obvious than with Docker compose and you would probably need to get into k8s/k3s/nomad territory in order to orchestrate a proper fleet.

[–] [email protected] 5 points 1 year ago

Thank you for the hard work! Enjoying Lemmy.world quite a bit. :)

[–] [email protected] 5 points 1 year ago

Thanks for the update. I especially like the transparency on not only the β€œupgrade” itself but also the potential issues encountered, together with the solutions. Seems rare nowadays, or I’m just seeing less and less people doing this.

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

To everyone having a login problem, it seems that resetting the password solves the issue! Maybe this means that the upgrade corrupted the stored hashes somehow?

load more comments (7 replies)
[–] [email protected] 5 points 1 year ago

thank you for letting us know behind-the-scene stuffs.

me myself is a sysadmin and really like story of successfully scaling up servers. very satisfy to hear.

once again, thank you!

[–] [email protected] 5 points 1 year ago

Fuck yeah upgrade hype

load more comments
view more: β€Ή prev next β€Ί