Slashzero
- 3 Posts
- 13 Comments
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Workaround for the performance issue with posting in large communitiesEnglish4·2 年前Yes. Absolutely does happen on other instances that have thousands of users.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Workaround for the performance issue with posting in large communitiesEnglish4·2 年前That actually sounds like something I would have enjoyed. I joined Reddit around the time it started taking over, I think.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Workaround for the performance issue with posting in large communitiesEnglish3·2 年前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.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Workaround for the performance issue with posting in large communitiesEnglish1·2 年前I really hope someone is doing some level of performance testing on those changes to make sure the changes fix the performance issues.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Workaround for the performance issue with posting in large communitiesEnglish10·2 年前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.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Workaround for the performance issue with posting in large communitiesEnglish92·2 年前Oh, Big-O notation? I never thought I’d see someone else mention big O notation out in the wild!
:high-five:
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Lemmy.world starting guideEnglish1·2 年前I did see it, thanks. I’m hoping to find some time to contribute this week.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Lemmy.world starting guideEnglish0·2 年前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.
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Lemmy.world starting guideEnglish0·2 年前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.
Slashzero@lemmy.worldtoLemmy Support@lemmy.ml•different states of the same post in different instances?English1·2 年前This sounds like a bug…
Slashzero@lemmy.worldto Lemmy.World Announcements@lemmy.world•Installed Lemmy 0.17.4-rc1English0·2 年前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.
I checked this, and my lemmy.hconf file already has the host for pictrs set to http://pictrs:80.
The only thing that has worked so far is manually unsetting my site’s image icon by unsetting it directly int he Database.