WIth the 1.14.60.5 release, I'm seeing a lot higher CPU usage (running on Linux). With a single user connected, it's using 60% of a 2.8GHz core and hovers between 90-100% with two users. I don't recall it being that bad on the previous version.
I think as a result of that, I'm getting a ton of lag as I move across chunk boundaries. This is only apparent when there is more than one person on the server. It doesn't occur on every chunk, and the location of the other player seems to have some effect on which boundaries cause the lag spikes.
I thought it might be something specific to our home base chunks, but we also had the same issue far away as we raided an ocean monument >3000 blocks away (with only 2 people connected, both in the monument).
I've attached a video clip, and you can see whenever I cross the chunk boundary, there is a pause in the game, that is experienced by both connected users (even if the other user isn't even moving).
Linked issues
Attachments
Comments 11
migrated
Doing a little more digging, and it seems like the lag happens when the second player's character renders because it's close enough to mine (or vice versa).
Could it be a delay in downloading the other player's skin from the character creator?
If it helps, our client is Nintendo Switch.
Doing a little more digging, and it seems like the lag happens when the second player's character renders because it's close enough to mine (or vice versa).
Could it be a delay in downloading the other player's skin from the character creator?
If it helps, our client is Nintendo Switch.
This isn't chunk generation lag (although that's a separate issue we've run into). These chunks have been long generated, and as it video clip shows it happens over and over for the same chunk.
This isn't chunk generation lag (although that's a separate issue we've run into). These chunks have been long generated, and as it video clip shows it happens over and over for the same chunk.
The video doesn't match your description though. The description I'm confident is BDS-2574 (even if its not chunk generation - BDS-2574 is just the drop in Linux performance, my hypotheses are just educated guessing based on the reports we've had and my own testing) but I've removed the dupe request until we can narrow down the freeze a little more.
Your description mentions high CPU usage which I would expect to cause block placement lag etc, the video demonstrates a client freeze which likely isn't server related. Because the movement is client authoritative what you should see is the client keeps moving and then "rubber bands" back to the position the server thinks it should be at.
You mention this happens when in range of a player, is it specific to this one player or does it happen when in range of any player? I'm not seeing this behaviour on my server so it will help to narrow down the issue.
Edit: We would also need to replicate the issue on supported devices (switch does not support BDS in any form so can't be accepted as a bug).
OK, maybe this is not a BDS issue, but a client issue then. I only have two users on the server so maybe we both get the freeze because we're both having the same client issue as we come into each other's view.
OK, maybe this is not a BDS issue, but a client issue then. I only have two users on the server so maybe we both get the freeze because we're both having the same client issue as we come into each other's view.
OK, I think you can close this and I'll open up a new ticket for the bedrock codebase in general after doing a little more digging tomorrow.