Yes. Absolutely does happen on other instances that have thousands of users.

That actually sounds like something I would have enjoyed. I joined Reddit around the time it started taking over, I think.

That’s pretty neat! I’ve honestly never seen it mentioned on Reddit before, so got a bit excited to see someone mention it here, admittedly maybe too excited.

I really hope someone is doing some level of performance testing on those changes to make sure the changes fix the performance issues.

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.

Oh, Big-O notation? I never thought I’d see someone else mention big O notation out in the wild!

:high-five:

I did see it, thanks. I’m hoping to find some time to contribute this week.

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.

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.

OMG! You are right. It’s my time to shine!

This sounds like a bug…

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.

• Not sure if you are aware, but I never received any emails about my signup being accepted. I just tried to log in on a whim and saw it worked. You might want to check your smtp settings to verify emails are going out. the approval email was in my spam folder.
• Saving (new or edit) a comment is taking 20-30 seconds (just timed saving this edit).

Ok. Now that I think about it, you shouldn’t have to specify the port.

You might want to add the secure port (:443) in your redirect. Otherwise it might be trying to load https on port 80 still, which can’t work.

• http: port 80
• https: port 443

Notes:

• just a guess. I haven’t looked at an nginx config in a while
• make sure to try on multiple browsers as they all don’t behave the same way