https://timings.aikar.co/?id=64e8fc3760644c16a8c0815b4d57beb4
Since I updated to 1.14.4, my TPS have dropped down significatly. I used to have 20tps with 50 players. Now I have 6-7tps.
I can't/I don't know how to identify the issue. In the timings I think the lag comes from Minecraft::tickEntity - nms.EntityEnderCrystal. But everytime I get a timing, the name of the entity at the top changes. Sometimes it is Horse, ItemFrame... It is very strange.
Paper: https://pastebin.com/jUfwTQAK
Spigot: https://pastebin.com/RcNa8Us4
Bukkit: https://pastebin.com/X8h11jFZ
183 (1.14.4)
I've started with 1.14.4 but the tps are now significantly low: https://timings.aikar.co/?id=3653e7c1633c448d9f6663108893eee3#
I didn't had such big amount of Sheeps and Turtles on loaded chunks to have such issues.
Timings or Profile link:
https://timings.aikar.co/?id=64e8fc3760644c16a8c0815b4d57beb4
Description of issue:
Since I updated to 1.14.4, my TPS have dropped down significatly. I used to have 20tps with 50 players. Now I have 6-7tps.
I can't/I don't know how to identify the issue. In the timings I think the lag comes from Minecraft::tickEntity - nms.EntityEnderCrystal. But everytime I get a timing, the name of the entity at the top changes. Sometimes it is Horse, ItemFrame... It is very strange.bukkit.yml, spigot.yml, paper.yml, server.properties
Paper: https://pastebin.com/jUfwTQAK
Spigot: https://pastebin.com/RcNa8Us4
Bukkit: https://pastebin.com/X8h11jFZPaper build number:
183 (1.14.4)
bukkit.yml - set this ;
spawn-limits:
monsters: 10
animals: 5
water-animals: 2
ambient: 8
ticks-per:
animal-spawns: 5
monster-spawns: 1
autosave: 6000
Have you been able to figure this out? I am experiencing the same problems.
Hey! Try to use this plugin :p
https://www.spigotmc.org/resources/entitytrackerfixer-fix-1-14-4-entitytick-lag.70902/
Regards
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in a long time. If the issue still applies to the most recent supported version, please open a new issue referencing this original issue.