this post was submitted on 28 May 2024
9 points (100.0% liked)
Reddthat Community and Support
713 readers
1 users here now
Reddthat Community & Support
This community is for us to chat about anything and everything, including support topics!
There is no defining specific rules for this community and it can be anything from "I do not like the weather" to "I've won the jackpot and want to give all the money away to charity!" ๐
Before posting, have you read the rules?
Introductory Required Reading
For anything else, try a search and see what turns up, if not post away!
Alternative Matrix Chatroom:
Alternative Support Forums:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thanks. I'm still seeing some long load times, so it looks like the issue is still present.
Do the RC releases have the federation changes to ditch the sequential transfer model? If so, I wonder if the DB is getting hammered or something...
No it doesn't (unfortunately). We have a proxy in the EU close to LemmyWorld which batch sends requests to our local queue, which then inserts them into Lemmy. We can sustain over 30/s and our db barely struggles. The DB isn't the problem as we have a stupid amount of resources at our disposal.
The majority of the time (in my experience with these issues) is that the developers are making changes to how Lemmy works and it inadvertently goes from a query that performed super fast, to a query that is not optimised.
Because we are on the beta tags (for this release only!) we have to weather the storm, but as soon as 0.19.4 is released we'll go back to only using the production ready releases instead of the beta ones.
I have some time today to do a thorough investigation now so I'll find the bad query, make an issue, and if it's a simple fix it will be rolled out within 24/48 hours.
Got it. Best of luck in your bug hunt!
Are you still getting the long load times? We have updated multiple times since then and I haven't found anything obvious which would be causing issues. Cheers
I was getting it a few days ago, but I'm pretty sure you weren't on 0.19.4-rc.11 yet the last time I saw it. Testing for a few minutes just now I haven't managed to reproduce it. Will let you know if I see the issue again. (Hopefully it's just good now!) Thanks!
I did find a small issue while checking though -- on mlmym's settings page, the logo in the top left is showing up with src
%3cnil%3e
instead of a valid path.Yep the underlying bug was finally fixed in -rc.11.
Basically our logo died every time the container restarted as it was never properly saved.
I'll fix our logo backup soon