Nicko van Someren
Assigned
No issues.
Reported
No issues.
Comments
Yes, it seems to still be an issue. Running an idle 19w07a server on my machine it takes up 101% CPU, so clearly some thread is still in a spin loop.
I was hoping that even if they don't do nanoseconds the might at least to microseconds 🙂
If you are in to bytecode editing you could try using Thread.sleep(0, 1000) instead of {{Thread.sleep(1) }}since you can pass either a number of milliseconds or a number of milliseconds and a number of nanoseconds. In the event that that fixes the tick time issue you could then play around with that second value to find a setting that gives acceptable tick time and acceptable CPU load.
On my server machine (Ubuntu 18.04, 2x8 core Xeon) things are better but still not perfect with 19w11a. The machine is running one instance using 19w11a and two using 1.13.2. The newest server is idling around 16% of a CPU and while the others are idling at about 2%. While this is a great deal better than the 100% it was using until now, it would be great to get it back to where is was in previous releases. Hopefully it's just due to excessive debugging code in the pre-release version.