
@lemmy.world
Have you tried enabling the slow query logs @ruud@lemmy.world? I went through that exercise yesterday to try to find the root cause but my instance doesnโt have enough load to reproduce the conditions, and my day job prevents me from devoting much time to writing a load test to simulate the load.
I did see several queries taking longer than 500ms (up to 2000ms) but they did not appear related to saving posts or comments.
Note: this seems like it has something to do with the database, and something getting royally messed up post upgrade.
After trying all sorts of network hacks and updates, I eventually just decided to backup my Postgres container, and nuke it.
With a fresh Postgres DB running along with 0.18.0, my self hosted site is back online. Of course, my local post history and all my subs are gone... but at least my site is operational again.
I'd advise anyone self-hosting to not upgrade to 0.18.0 yet.
The footer still shows the old versions, by the way. It does feel snappier than earlier for sure.
Iโm setting up my own instance to mess around with as well. Iโve got it running via Docker. The SSL setup was a pain, not really documented well. Also pictrs is giving me issues complaining about DB access.
The redirect is tricky and works in some browsers, but not others.
Edit: save took about 10 seconds, which is better than 20-30 seconds!
Edit 2: the footer shows the updated versions, now.
Actually the approval email was in my spam folder. My bad!
Thanks for looking into the save issue. Iโm looking into setting up my own instance now on a digital ocean droplet maybe, so I can maybe debug a few things on my own.
Would be funny if it was missing an index and doing a full table scan for some odd reason...
I focus on application performance in my day-to-day work, and missing indexes, greedy upoptimized queries, etc, are the root of a lot of issues. Hopefully you can get to the bottom of it.
Quick note: I'm not seeing a big delay (10+ seconds) when posting or saving on lemmy.ml, or my own instance.
I suppose I could, but, I've honestly spent the majority of today on lemmy answering "support" questions for people lol... Maybe I can try to take a look tomorrow. ๐คท
Actually, saving edits on lemmy.ml is also slow, about 4-5 seconds. Itโs probably a combination of user load and non-optimized queries.
thanks for using Leebra!
go to feed...