946

Lemmy.world status update 2023-07-05 (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world

195 comments fedilink hide all child comments

Another day, another update.

More troubleshooting was done today. What did we do:

Yesterday evening @phiresky@phiresky@lemmy.world did some SQL troubleshooting with some of the lemmy.world admins. After that, phiresky submitted some PRs to github.
@cetra3@lemmy.ml 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 @phiresky@lemmy.world , @cetra3@lemmy.ml , @stanford@discuss.as200950.com, @db0@lemmy.dbzer0.com , @jelloeater85@lemmy.world , @TragicNotCute@lemmy.world for their help!

And not to forget, thanks to @nutomic@lemmy.ml and @dessalines@lemmy.ml 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 4) 35 comments

sorted by: hot top controversial new old

[-] karthan@lemmy.world 1 points 1 year ago

Glorious, Ruud!

[-] MrPoopyButthole@lemmy.world 1 points 1 year ago

The server is absofuckinglutely flying today! It feels smooth and bug free!!! You guys are legends.

[-] Timou@lemmy.world 1 points 1 year ago

So that's why it was so smooth today... Great work!

[-] Reverendender@lemmy.world 1 points 1 year ago

I tried to enable push notifications and the app crashed. Also, how do I create a community?

[-] BitOneZero@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Good to see a heavy production server taking on the scaling issues. Thank you! To discuss Lemmy performance issues, there is a dedicated community: !lemmyperformance@lemmy.ml

[-] zikk_transport2@lemmy.world 1 points 1 year ago

Can you describe your setup? Single instance or multi-node setup behind load balancer?

[-] ruud@lemmy.world 1 points 1 year ago

1 big server with nginx load balancing to the docker containers running Lemmy

[-] TheVampireSaga@lemmy.world 1 points 1 year ago

Thank god, wasn't able to use the site lol

[-] Zrob@lemmy.world 0 points 1 year ago

Awesome work. Any way other devs can contribute?

[-] MrPoopyButthole@lemmy.world 0 points 1 year ago

Go checkout the Github issues for Lemmy

load more comments (3 replies)

[-] cheerjoy@lemmy.world 0 points 1 year ago

I love how open you guys are when it comes to running the server! Much nicer than lemmy.ml imo

load more comments (1 replies)

[-] xandertron@lemmy.world 0 points 1 year ago

upvoting posts is so much more stable now, we might actually see more bean posts as a result

[-] Labotomized@lemmy.world 0 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 :)