this post was submitted on 23 Jun 2023
18 points (100.0% liked)

Lemmy

2172 readers
1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago
MODERATORS
[email protected]
18
FYI: lemmy.ml is down now, hours after the upgrade to release 0.18.0 - EDIT: over 2 hours down, but BACK UP now! (self.lemmy)
submitted 1 year ago* (last edited 1 year ago) by BitOneZero to c/[email protected]
13 comments fedilink hide all child comments
 

504 Gateway Time-out nginx timeout error on home page

you are viewing a single comment's thread
view the rest of the comments
[–] BitOneZero 1 points 1 year ago* (last edited 1 year ago)

0.17.4 has a lot of the same problems, so going forward is the only hope. The amount of messages and peer servers alone are causing fundamental performance problems with the code, regardless of 0.17 or 0.18.

People taking down their servers to upgrade to 0.18 could have triggered a swarm of resource problems on the central federation instance that they had never experienced when there were only a dozen(?) other Lemmy instances 2 months ago.