We’re still working to find a solution for the posting slowness in large communities.
We have seen that a post does get submitted right away, but yet the page keeps ‘spinning’
So right after you clicked ‘Post’ or ‘Reply’ you can refresh the page and the post should be there.
(But maybe to be sure you could copy the contents of your post first, so you can paste again if anything would go wrong…)
Does this behaviour appear on other big instances? E.g. lemmy.ml?
Yes. Absolutely does happen on other instances that have thousands of users.
I assume that there is something that is O(N), which explains why wait time scales with community size (amount of posts, comments)
its def more hung up today, oddly its only first level replies for some reason
I noticed this, thanks for the clarification
Been noticing this in the app I’m working on. Pretty much all POST requests fail to return a response and just timeout after 60 seconds. A quick refresh shows that the new items do successfully get created though.
ok, so it’s not just me. Hope it gets resolved soon!
I’ve done this twice in the last 20 minutes and the content is not there. This workaround was working earlier today though.
At least the “reply” button goes away so I don’t end up double- triple- or even duodecuple-posting! Thanks for all the hard work that must be going on behind the scenes right now!
I kept getting a timeout message from Jerboa which led me to think I hadn’t been posted. So I ended up submitting the same joke to the Dad Jokes sub three times. Which actually is how dad might tell that joke.
Lemmy is now your digital dadlife assistant.
@[email protected] Yo dude, first off huge props and a big thank you for what you have setup. I’ll be donating monthly while I am here. I appreciate that we have an alternative to Reddit at this critical moment in time.
I do have a question on your long term plans, do you want to continue to expand and upgrade the server, as funding allows, or is there a cap that you will close off the server to new members? Or perhaps make it more of a process to join?
Well if all the Reddit users would get over to Lemmy I guess all servers would need to scale up… but I think the server we have now is powerfull enough to grow quite a lot, as long as the software gets tuned …
Is the slowdown that it the instance has to send out updates about the comment to every other instance before returning a successful response? If so, is anyone working on moving this to an async queue?
Sending out updates seems like something that’s fine being eventually consistent
Ooh that’s a good remark ! I’ll see if that’s the cause
Reading more about how this works, sending out updates to each instance shouldn’t block the request from returning unless you have a config flag set to debug source.
It might be due to poorly optimized database queries. Check out this issue for more info. Sounds like there are problems with updating the rank of posts and probably comments too
Nice teething problems. I tried to post to [email protected] but it just kept spinning. When I refreshed the post was not there.
