Lemmy.World Announcements

29105 readers

12 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email [email protected] (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 2 years ago

MODERATORS

208

Workaround for the performance issue with posting in large communities (self.lemmyworld)

submitted 1 year ago by ruud to c/lemmyworld

62 comments fedilink hide all child comments

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..)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 21 points 1 year ago (6 children)

Keep in mind that the upcoming Lemmy update will probably fix this I think. (Replacing websockets)

[–] RoyalEngineering 6 points 1 year ago (3 children)

Maybe this is a dumb question, but why would replacing websockets speed things up? I read the Wikipedia page on it, but I guess I don’t understand it fully.

[–] phiresky 7 points 1 year ago (2 children)

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.

[–] [email protected] 4 points 1 year ago

The caching problem is definitely part of it from conversations on GitHub.

[–] RoyalEngineering 4 points 1 year ago

Thanks for the explanation!

load more comments (2 replies)