Thomas Kolar
- ralokt
- ralokt
- Europe/Stockholm
- Yes
- No
3 issues
Key
Summary
Status
Reporter
Assignee
Created
MCL-9366
MC-134065Large numbers of stacked boats cause significantly more lag than they used to
Awaiting Response
Added Attachments:
Added Attachments:
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Thomas Kolar Do you happen to have a server log from before that restart that you could attach to the ticket?
To my knowledge, the world was only ever loaded in vanilla survival. Since we're a snapshot server, there may be associated weirdness, though.
And yes, there are quite a few signs in the area.
I was able to reproduce this. Connected to a server without problems, entered a minecart, instantly got this error.
Reconnecting with 1.9.1pre3 worked, and I was inside the minecart.
There is at least a fourth category here:
4. Players who may produce entity cramming situations unintentionally
In any case, those categories are not exhaustive. People can be affected, not have a preference, and still not want to be surprised that their mobs are dying...
Also, as someone who belongs to 2.1, this is not satisfactory. If some people will "simply have to deal", then we should make sure that what they "simply have to deal" with is a good idea; making it necessary to evaluate all alternatives and find the best one for this group, if the goal is to take all players into account. Of course we're not all players, and what other people want may be more important, which is OK. But handwaving the issue away by saying "well, SOMEONE will always be mad" makes me sad
I understand the need for this gamerule for reasons of performance and feasibility of feature parity/compatibility. The nice thing is, though, different compatible versions can still have different defaults as long as they can deal with all alternatives, and I would really appreciate not having this "on" as a default.
EDIT:
Also, I started writing this before we were asked to cease discussion here, and didn't see the post in time; Sorry about that.
It would be awesome if this were addressed. It's really frustrating to have the equivalent of 3-4 transatlantic flights on record, only for that to be reset. A fix would be as simple as to use long instead of int for statistics.
I am experiencing the same issue. Unfortunately, the world I am playing on is huge (Quite a few Gigabytes in size).
What I tested:
Anomalies preceding the bee strike:
Additional random potentially useful information:
I'll try to reproduce the problem on a truncated copy of our world in the next days, perhaps I can provide a world download then.
Restarting the server fixed the issue for me.
loganon.log
Sorry, I completely forgot about this issue - but here is an anonymized log with player names, GUIDs and IPs replaced. I'm sceptical that it'll help much, though, there's hardly anything out of the ordinary in there.
However, there is one thing maybe worth noting: We were experiencing regular crashes due to OOM conditions at the time, and have fixed those in the meantime by setting `-Xms` and -Xmx` to the same value. I can't remember this issue happening recently, and I believe it's the only significant change we made to our deployment.
It seems to have gotten much better, although I can't really compare since we had to remove those launchers and are on different hardware now.
But at the very least, building launchers where boats are not inside water is now feasible for us again (for some reason, boats in water cause significantly more lag).
Seed: 8470219322699000237
Approximate coordinates in screenshot: -47, 75, -18
Why is this resolved? it's really easy to reproduce, and it's still happening in 1.19...
MC-153048is another instance of this. This issue is also marked as "can't reproduce" which I find very hard to believe - I'm currently having trouble not reproducing it while attempting to build a boat elevator...