The released 1.14 server .jar is still affected (I do not know how to correlate the NNwNNa snapshots to the releases, sorry).
I host 4 minecraft server instances on an Arch Linux amd64 machine, and due to this issue I had to suspend hosting after I upgraded from 1.13.2 to 1.14.0. I can definitely see how one could get a nasty surprise when hosting this on a cloud service.
The 1.14 server .jar file has been obtained from here.
Here is a commented screenshot from a graphical systems load indicator when stopping, then starting, and then stopping again the 4 service instances:
[media]
The baseline idle CPU load can be seen pretty well.
The shown time window is 4 minutes (120px, 1 pixel = 2 seconds), so yeah the huge startup load is pretty bad too, I am quite sure 1.13.2 started up in a fraction of that time. This is not an embedded system or anything, it is an entry-level server, the CPU being an Intel Xeon E3-1225 v3 with 4 cores and 3.2 GHz having 32 GiB of memory.
Java runtime environment:
openjdk version "1.8.0_212" OpenJDK Runtime Environment (build 1.8.0_212-b01) OpenJDK 64-Bit Server VM (build 25.212-b01, mixed mode)
eomanis
The released 1.14 server .jar is still affected (I do not know how to correlate the NNwNNa snapshots to the releases, sorry).
I host 4 minecraft server instances on an Arch Linux amd64 machine, and due to this issue I had to suspend hosting after I upgraded from 1.13.2 to 1.14.0. I can definitely see how one could get a nasty surprise when hosting this on a cloud service.
SHA-384 checksums here:
951dbcef3af5f952cafb9a89379aed2018d8eebe4e9ebf801bd03c44719931d8652ddc7dab83f0d26e2568e8add4b788 minecraft_server.1.13.2.jar
2e691ee6bc50f67b9ad2237d86c30e7394aba39d73e20fa43b535f1c74b01238a8724965fdb22c1b3f52501f94005fe6 minecraft_server.1.14.jar
The 1.14 server .jar file has been obtained from here.
Here is a commented screenshot from a graphical systems load indicator when stopping, then starting, and then stopping again the 4 service instances:
[media]The baseline idle CPU load can be seen pretty well.
The shown time window is 4 minutes (120px, 1 pixel = 2 seconds), so yeah the huge startup load is pretty bad too, I am quite sure 1.13.2 started up in a fraction of that time. This is not an embedded system or anything, it is an entry-level server, the CPU being an Intel Xeon E3-1225 v3 with 4 cores and 3.2 GHz having 32 GiB of memory.
Java runtime environment:
openjdk version "1.8.0_212"OpenJDK Runtime Environment (build 1.8.0_212-b01)OpenJDK 64-Bit Server VM (build 25.212-b01, mixed mode)