The problem is less in 1.14 than it was in some earlier snapshots, but despite high resource usage the server still lags behind quite often and for a long time, sometimes seconds at a time. I still run 1.7.10 and older, which even with mods don't come close to the same resource usage nor experience the fairly extreme timeouts. With two players using the same connection to a server less than 400miles away on a completely barren map still use 60% of 800% total is not acceptable, especially when timeouts and lag are still present. The fact this issue is being completely ignored, while other completely trivial bugs seem to get more attention is disgusting, shame on you Mojang!
I have run a couple debugs now, all showing tickrate slowing down and often taking more than 100ms with just a single player. Meanwhile cpu spikes of 20-40% and 4 times the idle usage compared to 1.7 versions. Tried multiple java versions along with zulu and official oracle binaries, tried vanilla, Spigot and even ran builds from other systems in case something was wrong there. Started experiencing lag and unresponsive behavior in singleplayer now too. This is not acceptable! 1.14.2 as of this post is not in any playable state. I frankly don't know what has happened, but since 2 major versions this has only gotten worse.
I can see why the thought comes to mind that "someone" is trying to kill the java version, even if unintentional, it is working. If it wasn't for the fact Win10 was such a disastrous POS as well. Mojang, with all due respect, fix the product I paid for!
You show a complete disregard of this issue. I have modded 1.7.10 servers running on the very same hardware, generating chunks like crazy without seeing such severe and consistent issues. Since 1.12 1.13 the server and singleplayer performance has gone down massively. Constant and I mean constant high tick timings and server crashes from ticks taking 10 seconds or more. In contrary 1.7.10, with mods, more players and built worlds run better and more consistently with less tick time.
I am just guessing, but some "improvement" meant to increase multithreading just causes lots of dead threads that slow down finishing up ticks resulting in them consistently taking longer. These issues have since 1.14 penetrated into singleplayer, heck I keep hearing about issues outside of our servers daily. The fact these issues are being entirely ignored by Mojang is infuriating so many people now. The handling of bugs and priority given to things that are trivial to near impossible to reproduce is killing the game. We now have sluggish servers consuming 4 times the resources, singleplayer worlds that won't allow for proper combat against mobs and blocks that lack interface or clear purpose as of yet. This update has had one of the most rocky starts in the history of the game. We have had this before, but eventually things stabilized. Since Bedrock and M$ came along the quality has declined and the updates have gone back to levels of 1.3.2, if you remember that mess.
It frankly is not acceptable how the game runs and throwing hardware at the problem is not a solution, long or short term, if we did this for everything there would be no innovation or optimization. Given how widespread the issue is becoming and how obvious it is once you start digging just a little bit I wonder if you actually spent some time running profiling or comparing versions in a controlled environment. Only because you are unable to reproduce a problem or have somehow found a way to ignore it does not mean it does not exist and it much less means that it does not need investigation and attention, especially given how many have reported this and continue to report it for literally every version that is released.
The problem is, seeing a ton of trivial bugs fixed on each pre which gives the impression that not everyone is working on solving an issue that has made the game pretty much unplayable and that feels very much like a slap in the face.
This is not just about server performance seeing as tested in this case means firing up a singleplayer world and running the profiler there seeing the same results as before almost to the millisecond. Fresh world, fresh installed, even rebooted before doing it to clear memory. Have done the same exact test for each time a new snapshot or pre has come out, all the way back to 1.13. the results are not improving and I have indicated that on both this and the other issue about the performance. Many have followed to do the same, yet the lack of official statement is what gets so many riled up about this. All this testing, data and confirmation a problem exists. The fact they are aware of it is nice, but an official "We know, here is what we will try to fix it" would be nice. I know very well how boilerplate that part is and that it could mean anything, but performance has only deteriorated over time, hence this and other reports, so even the slightest hint toward increased performance while not specifying what that is and still getting the same profiling results feels like a slap in the face to me, sorry for being so human.
I'm sorry for making such a wind, sure, it is not nice, but someone has to be this blunt. I setup a modded server, 50 or so mods, on 1.12.2. Both it and the totally vanilla server are now there idling, no players, only the spawn area being chunkloaded. Guess which one is consuming more cpu time... It's painful, honestly just painful to play the game this way. Even in singleplayer being teleported back due to tick timeouts, dying because of that, killing your favorite pet because the game thought it was in the way. It is becoming an unplayable state no matter single or multiplayer.
I do hope that we will eventually get some form of official statement as to even a hint at what they think may be wrong and what is being attempted to fix it, because as it stands Minecraft Java Edition is not in a playable/enjoyable state.
100%, single thread, server on Ubuntu entirely unusable in this format. Tried all sorts of java arguments, no dice.
This needs fixing asap!
Watching the recent changelogs and bugs being fixed, but apparently this is not a priority, shame!
The problem is less in 1.14 than it was in some earlier snapshots, but despite high resource usage the server still lags behind quite often and for a long time, sometimes seconds at a time. I still run 1.7.10 and older, which even with mods don't come close to the same resource usage nor experience the fairly extreme timeouts. With two players using the same connection to a server less than 400miles away on a completely barren map still use 60% of 800% total is not acceptable, especially when timeouts and lag are still present. The fact this issue is being completely ignored, while other completely trivial bugs seem to get more attention is disgusting, shame on you Mojang!
I have run a couple debugs now, all showing tickrate slowing down and often taking more than 100ms with just a single player. Meanwhile cpu spikes of 20-40% and 4 times the idle usage compared to 1.7 versions. Tried multiple java versions along with zulu and official oracle binaries, tried vanilla, Spigot and even ran builds from other systems in case something was wrong there. Started experiencing lag and unresponsive behavior in singleplayer now too. This is not acceptable! 1.14.2 as of this post is not in any playable state. I frankly don't know what has happened, but since 2 major versions this has only gotten worse.
I can see why the thought comes to mind that "someone" is trying to kill the java version, even if unintentional, it is working. If it wasn't for the fact Win10 was such a disastrous POS as well. Mojang, with all due respect, fix the product I paid for!
@Mudassar Khan
You show a complete disregard of this issue. I have modded 1.7.10 servers running on the very same hardware, generating chunks like crazy without seeing such severe and consistent issues. Since 1.12 1.13 the server and singleplayer performance has gone down massively. Constant and I mean constant high tick timings and server crashes from ticks taking 10 seconds or more. In contrary 1.7.10, with mods, more players and built worlds run better and more consistently with less tick time.
I am just guessing, but some "improvement" meant to increase multithreading just causes lots of dead threads that slow down finishing up ticks resulting in them consistently taking longer. These issues have since 1.14 penetrated into singleplayer, heck I keep hearing about issues outside of our servers daily. The fact these issues are being entirely ignored by Mojang is infuriating so many people now. The handling of bugs and priority given to things that are trivial to near impossible to reproduce is killing the game. We now have sluggish servers consuming 4 times the resources, singleplayer worlds that won't allow for proper combat against mobs and blocks that lack interface or clear purpose as of yet. This update has had one of the most rocky starts in the history of the game. We have had this before, but eventually things stabilized. Since Bedrock and M$ came along the quality has declined and the updates have gone back to levels of 1.3.2, if you remember that mess.
It frankly is not acceptable how the game runs and throwing hardware at the problem is not a solution, long or short term, if we did this for everything there would be no innovation or optimization. Given how widespread the issue is becoming and how obvious it is once you start digging just a little bit I wonder if you actually spent some time running profiling or comparing versions in a controlled environment. Only because you are unable to reproduce a problem or have somehow found a way to ignore it does not mean it does not exist and it much less means that it does not need investigation and attention, especially given how many have reported this and continue to report it for literally every version that is released.
On the wiki it states for the new pre
Performance
I can confirm that that is a lie. Just tested, still the same performance outside some margin of error.
The problem is, seeing a ton of trivial bugs fixed on each pre which gives the impression that not everyone is working on solving an issue that has made the game pretty much unplayable and that feels very much like a slap in the face.
This is not just about server performance seeing as tested in this case means firing up a singleplayer world and running the profiler there seeing the same results as before almost to the millisecond. Fresh world, fresh installed, even rebooted before doing it to clear memory. Have done the same exact test for each time a new snapshot or pre has come out, all the way back to 1.13. the results are not improving and I have indicated that on both this and the other issue about the performance. Many have followed to do the same, yet the lack of official statement is what gets so many riled up about this. All this testing, data and confirmation a problem exists. The fact they are aware of it is nice, but an official "We know, here is what we will try to fix it" would be nice. I know very well how boilerplate that part is and that it could mean anything, but performance has only deteriorated over time, hence this and other reports, so even the slightest hint toward increased performance while not specifying what that is and still getting the same profiling results feels like a slap in the face to me, sorry for being so human.
I'm sorry for making such a wind, sure, it is not nice, but someone has to be this blunt. I setup a modded server, 50 or so mods, on 1.12.2. Both it and the totally vanilla server are now there idling, no players, only the spawn area being chunkloaded. Guess which one is consuming more cpu time... It's painful, honestly just painful to play the game this way. Even in singleplayer being teleported back due to tick timeouts, dying because of that, killing your favorite pet because the game thought it was in the way. It is becoming an unplayable state no matter single or multiplayer.
I do hope that we will eventually get some form of official statement as to even a hint at what they think may be wrong and what is being attempted to fix it, because as it stands Minecraft Java Edition is not in a playable/enjoyable state.