The title says it all. The attached profile results are from idling in our main nether hub, where there is a powerful elytra launcher (a couple of hundred boats) nearby [1].
This did not use to be a problem, but since 1.13, as the attached profile results indicate, the server runs at 3 TPS and is no longer playable.
Also, since there are two fairly weak launchers in the spawn chunks, the maximum attainable TPS are currently about 5-6 when idling at spawn.
In case it helps, we're a snapshot server and ran into lag issues a while back, when trying to upgrade to 17w46a. We subsequently ran 17w45b up to this point, trying the newest snapshot once or twice in between to see if it was playable. It's my strong impression that the issue is the same.
[1] Before someone doubts me, yes, I managed to build an elytra launcher in the Nether. It involved stacking them in the Overworld, teleporting them to the nether, and then pushing them through a hole in the bedrock ceiling with pistons while being VERY careful not to disturb them.
Attachments
Comments 5
I can confirm in 1.15.2 - A player built a boat-based elytra launcher and the server is constant throwing "Can't keep up!" messages in the console.
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).
I just upgraded from 1.14.X to 1.16.1 and this bug reappeared for me. Elytra launchers using boats stacked in a confined space hits the CPU hard.
Please check if that's still an issue for you in the latest 1.15.2 stable release.