this post was submitted on 05 Jul 2023
3319 points (99.4% liked)

Lemmy.World Announcements

29098 readers
176 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
 

Another day, another update.

More troubleshooting was done today. What did we do:

  • Yesterday evening @phiresky@[email protected] did some SQL troubleshooting with some of the lemmy.world admins. After that, phiresky submitted some PRs to github.
  • @[email protected] created a docker image containing 3PR's: Disable retry queue, Get follower Inbox Fix, Admin Index Fix
  • We started using this image, and saw a big drop in CPU usage and disk load.
  • We saw thousands of errors per minute in the nginx log for old clients trying to access the websockets (which were removed in 0.18), so we added a return 404 in nginx conf for /api/v3/ws.
  • We updated lemmy-ui from RC7 to RC10 which fixed a lot, among which the issue with replying to DMs
  • We found that the many 502-errors were caused by an issue in Lemmy/markdown-it.actix or whatever, causing nginx to temporarily mark an upstream to be dead. As a workaround we can either 1.) Only use 1 container or 2.) set ~~proxy_next_upstream timeout;~~ max_fails=5 in nginx.

Currently we're running with 1 lemmy container, so the 502-errors are completely gone so far, and because of the fixes in the Lemmy code everything seems to be running smooth. If needed we could spin up a second lemmy container using the ~~proxy_next_upstream timeout;~~ max_fails=5 workaround but for now it seems to hold with 1.

Thanks to @[email protected] , @[email protected] , @[email protected], @[email protected] , @[email protected] , @[email protected] for their help!

And not to forget, thanks to @[email protected] and @[email protected] for their continuing hard work on Lemmy!

And thank you all for your patience, we'll keep working on it!

Oh, and as bonus, an image (thanks Phiresky!) of the change in bandwidth after implementing the new Lemmy docker image with the PRs.

Edit So as soon as the US folks wake up (hi!) we seem to need the second Lemmy container for performance. So that's now started, and I noticed the proxy_next_upstream timeout setting didn't work (or I didn't set it properly) so I used max_fails=5 for each upstream, that does actually work.

(page 5) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago

Thank you so much! I will be donating a few cappuccinos your way when my next check arrives. I really appreciate how awesome of a community you’ve brought together & all of the transparency with the updates (and the frequency) is astounding! Keep up the great work but don’t forget to take breaks :)

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

Thank you to everyone that helped.

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

That's some pretty heroic shit right there.

You just took lemmy from something I'm willing to live with in the short term in hope it gets better, to something I am fully satisfied with.

Now let's grow so we can fuck it up all over again!!!

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

Was waiting for this update. Woke up a couple hours ago and Lemmy was working great so I knew y’all put in some time. Thanks for your efforts!

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

Good job on troubleshooting!

Have you looked into possibly migrating to kubernetes or some other form of docker container management/orchestration system to help with automatic scaling and load balancing?

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

Don't quote me, but I recall reading on GitHub that there are a few things to be refactored before Lemmy can support horizontal scaling approaches.

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

That's a very phallic bandwidth image Dr Freud

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

Thank you for all the hard work and transparency as always! Everything is running perfectly knocks on wood

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

It's really fun to see these updates, and get insight into what you're putting into this instance. It's real obvious that it's a labor of love.

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

Thanks for the update! Things seem way speedier now ^^

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

Thank you guys for all the hard work!!

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

damn bro, y’all coming in clutch to improve stability of this lemmy instance.

Good shit bros. Hope to contribute upstream and find more performance related bugs. I browsed the code for lemmy, and could not find any performance tests.

I can probably start there.

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

Thanks for all the work you've put into this!

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

Amezing improvement! Lemmy felt so much more responsive suddenly today, now it makes sense why :3

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

Everything is much faster and smoother today. Thanks devs!

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

Woo hoo, nice graphs! Monitoring data that shows big improvements is always fun to see.

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

Things feel a ton better today. Thank you for all the hard work!

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

The new updates made a ton of improvements. Thank you very much. It is near ideal now.

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

Seemed to be running a lot smoother, thank you Ruud!

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

Can confirm, having way less problem browsing lemmy right now. Thank you admins!

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

The instance seems to be much better. Posting and commenting is not taking as long and loading times are way better. I hope things can stay this good or even get better.

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

Things are looking a lot more stable, thank you (all) for the amazing work!

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

Fantastic job in troubleshooting and submitting PRs! Improvements are very noticeable already :)

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

am i amazed by you all guys work?!

i absolutely am

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

The changes are very much noticeable, thanks as always everyone!

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

You all are champions today. When I loaded this up today, I was very happy and impressed. I knew tweaks were made.

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

Upvotes appear to be working but I still can't post images. The post displays the infinite spinning loading circle.

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

Thanks for your efforts and improvements. Keep it going β™₯οΈπŸ™

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

Awesome update, great to see and feel the progress from all the hard work!

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

Wow! Your commitment and diligence is admirable!

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

Great work! Awesome to see how fast the technical side of the Lemmyverse is evolving and improving!

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