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…)
In general websockets scale badly because the server has to keep open a connection and a fair amount of state. You also can’t really cache websocket messages like you can normal HTTP responses. Not sure which reasons apply to Lemmy though.
The caching problem is definitely part of it from conversations on GitHub.
Thanks for the explanation!