Having tried to run a 1.13-pre1 server on MineOS the other day, and getting horrible performance, I decided to do a little investigating.
I’m running MineOS in a Docker container within unRAID. Created a server, logged in, and saw CPU usage on one thread jump to 100% - As expected when first loading a world. This stabilised after a few minutes, a couple of others joined, and we went about our business. After a few minutes though - when people started exploring and generating new chunks, the lag made the game unplayable, followed by a server crash.
Investigated more, and yes, this happens whenever new chunks are generated. a CPU thread gets pegged at 100%, the server can’t keep up and closes itself for being too far behind.
Tried making a server on my local machine, and it runs great. Also, all 8 threads are used.
Made a server on a Windows VM on the same unRAID box as before, and this also runs great, using all 6 threads.
Seems Minecraft has multithreaded chunk generation now.
Server on MineOS Docker in unRAID is locked to a single thread, causing the server to lag generating chunks, and crashing it.
Same server on Win10 VM runs perfectly fine, using several threads.
All default settings, as far as I’m aware.
Is there something in MineOS that was hard-coded a while ago for single-thread that can be changed, or is there something else causing this that I’m missing?