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, I just want to echo what everyone else is saying - thanks much for hosting + all the efforts to keep things working well. It’s appreciated 👍
Thank you Ruud for hosting! Your work is much appreciated.
Thanks for hosting this great instance! We appreciate all you’re doing!
Testing reply speed…
Something is weird.
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.
Have you noticed the issue?
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.
Yeah, I tried opening it again a few times, no luck yet. Will see if I can figure out any pattern.
I had something similar happen yesterday.
I opened a thread about pokemon, browsed it for a bit, did some stuff in other tabs, and clicked back to the pokemon tab maybe an hour later to browse some more.
The post had changed to one where a user was asking for relaxing game recommendations and it was loading in new comments that seemed to be from that post, but I could still see the comments that had already loaded from the pokemon post when I scrolled down.
When I refreshed it changed back to the pokemon post and only showed comments from that.
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
Docker is not necessary, lemm.ee for example is running without docker!
Here is documentation for setting it up: https://join-lemmy.org/docs/en/administration/from_scratch.html
Of course you can fully adapt it to your own use case. The Lemmy backend is a single binary, you don’t even need to build it on the same machine which will run it. There’s no hard requirement to use nginx or anything like that either - if you understand what this guide is doing, you can replace all the unimportant parts as needed.
Hehe, the joys of troubleshooting and profiling. Isn’t it fun?
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.
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?
@ruud@lemmy.world have you seen https://lemmy.world/post/72136 ?
That is definitely a good lead