They are actively working on improving the performance. Large distributed systems aren't the easiest thing to build and scale. E.g. here is where they are working on improving the compute time required to handle upvoting:
I'm new to this tech. Is it because of the across server action? Like sometimes when you wait for an email or a crypto to clear?
Its somewhat related, yes. Each time you do something in the web browser like upvote, that gets sent to your instance (e.g. lemmy.world). Then, the instance needs to update the other instances with that action (this is called publishing the action). Meanwhile, it needs to accept actions from other instances (these are actions that the server is subscribed to). All of these actions take server time and network so there is a queue of actions (think of this as each action standing in line waiting for its turn with the network/cpu).
You can optimize this a lot because each time you open a network connection and send something, there is some cpu and network cost above and beyond the action itself. So there are smart ways to group things together. But, the challenge is that such grouping adds delays (e.g. it may take longer for a moderator's removal of an offending comment to propagate to your server).
The post lagging seems to be front end only. So far I've had no issue simply refreshing the page when it hangs.
Anyone else getting lag when posting or upvoting?
Yes. When I post a comment, it lags so bad that I just open another tab to continue browsing.
Yes, sluggishness and timeouts. As others suggest, there are growing pains. I have faith that as the new number of users starts to stabilize, these problems will settle down.
There’s a recent post on this here: https://lemmy.world/post/90611
TLDR; They’re actively working on fixing it.
Growing pains. Awesome to hear they're fixing it.
They are actively working on improving the performance. Large distributed systems aren't the easiest thing to build and scale. E.g. here is where they are working on improving the compute time required to handle upvoting:
https://github.com/LemmyNet/lemmy/issues/3062
I'm new to this tech. Is it because of the across server action? Like sometimes when you wait for an email or a crypto to clear?
Its somewhat related, yes. Each time you do something in the web browser like upvote, that gets sent to your instance (e.g. lemmy.world). Then, the instance needs to update the other instances with that action (this is called publishing the action). Meanwhile, it needs to accept actions from other instances (these are actions that the server is subscribed to). All of these actions take server time and network so there is a queue of actions (think of this as each action standing in line waiting for its turn with the network/cpu).
You can optimize this a lot because each time you open a network connection and send something, there is some cpu and network cost above and beyond the action itself. So there are smart ways to group things together. But, the challenge is that such grouping adds delays (e.g. it may take longer for a moderator's removal of an offending comment to propagate to your server).
The post lagging seems to be front end only. So far I've had no issue simply refreshing the page when it hangs.
Yes. When I post a comment, it lags so bad that I just open another tab to continue browsing.
Yes, sluggishness and timeouts. As others suggest, there are growing pains. I have faith that as the new number of users starts to stabilize, these problems will settle down.
Yes lots of lag!