[Done - for now...] Expect some brief restarts today (Jun 12 CET)
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..
Hey. From my own experience - Nginx is awesome and fast when it is working, but the more you want from it, the more difficult it becomes.
Give Caddy a try. This reverse proxy has always been excellent for me. It has HTTP3 (QUIC) support, automatic ACME and overall excellent configuration in terms of simplicity and user friendliness.
Caddy is not a good choice if you need TCP/UDP proxy. It's only HTTP/HTTPS proxy.
Someone said this about Caddy "it injects advertising headers into your responses". Is this true? I don't know anything about caddy but that doesn't sound too good lo (to be fair it could be misinformation).
I opened this post from main page "subscribed listing", but the title showed "I can't find any cannabis cultivation community", but the comments were same. I initially thought I have opened a wrong post, but the comments were mentioning "Good work Ruud", so I refreshed and it fixed post's title.
It's happened to me a few times as well (not just on this instance, think it's a bug in Lemmy itself). So far I'e not found a reproducible pattern though so it's a tricky one to bug report effectively.
Since I have you here, if I start my own instance do I absolutely have to use docker? I've never had good experiences with it and would rather just install programs the old-fashioned way
Oh wait, that’s because I’m posting to Lemmy.world from my instance. It’s only slow when posting to Lemmy.world from a Lemmy.world user.
With that in mind, it makes me think it has something to do with some insert or update that happens. My local DB is not under load, so my save is fast. Lemmy.world’s DB is under load so the save is slow.
It might not even be the insert/update that is slow. Could be some other insert into another table that gets triggered on save that is the culprit.
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?