Lemmy.World Announcements

28381 readers

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

333

[Done - for now...] Expect some brief restarts today (Jun 12 CET) (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

98 comments fedilink hide all child comments

I'm trying to fix this annoying slowness when posting to larger communities. (Just try replying here...) I'll be doing some restarts of the docker stack and nginx.

Sorry for the inconvenience.

Edit: Well I've changed the nginx from running in a docker container to running on the host, but that hasn't solved the posting slowness..

you are viewing a single comment's thread
view the rest of the comments

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

Any progress on this. I've been thinking about it too. Couple of ideas:

Too many indexes needing to update when an insert occurs?

Are there any triggers running upon insert?

Unlikely but there isn't a disk write bottleneck? Might be worth running some benchmarks from the VM shell.

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

I was thinking that as well, it’s like the post gets “checked” or something like that and that gives a timeout of 20secs. It could be an api or database but somehow my spidey sense says this could well be in code. Some extra calls to filter things maybe? Using an external server? Or even the propagation to the others? (Idk how this federation thing connects to the others, could be just that; maybe another server that is the bottleneck) I just found the 20 seconds suspicious given that is the default timeout

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

Didn't know about the timeout but that makes sense. Would be easy to test by changing the nginx timeout.

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

Another thought: how many db connections do you have? Could it be starved because there are so many selects happening and it needs to wait for them to finish first?