I always have only one processor core loaded on the server. Is multithreading not supported? What am I doing wrong?
Comments 2
You've not provided much information to know for sure but there are a few different reasons for what you're seeing.
1. We have an open issue BDS-2574 for Linux Performance problems. While not specifically an issue with only running a single core its presented in a number of different ways.
2. You're mistaking "multi-threading" for meaning it uses all cores equally or in large amounts.
3. Changes have been made to the server.properties threading option.
Most of the reports that come in are for option 2. Bedrock Dedicated Server (and Minecraft Bedrock) are demonstrably multi-threaded. However, not all workloads are created equal. Much of the work is still contained to a main game thread. This is the single core usage you are seeing. You will however see increased usage of other cores for things like passive mob pathfinding if you chuck a bunch of cows on lower half slabs.
Everything below are just my assumptions
Java is heavily dependent on the famous "tick". This is that a tick processes a whole bunch of the world, and then moves onto the next tick. I suspect Bedrock, to keep the same feel, had to do something very similar which has them using a single thread for the main game. Where possible they've spun off behaviours not dependent on game ticks (like path finding as an example).
But you can imagine, if Redstone was completely seperated from the main game processing, things could go horribly awry with all sorts of contraptions.
In either case, this unfortunately doesn't meet the criteria for a bug. Best of luck
You've not provided much information to know for sure but there are a few different reasons for what you're seeing.
1. We have an open issue BDS-2574 for Linux Performance problems. While not specifically an issue with only running a single core its presented in a number of different ways.
2. You're mistaking "multi-threading" for meaning it uses all cores equally or in large amounts.
3. Changes have been made to the server.properties threading option.
Most of the reports that come in are for option 2. Bedrock Dedicated Server (and Minecraft Bedrock) are demonstrably multi-threaded. However, not all workloads are created equal. Much of the work is still contained to a main game thread. This is the single core usage you are seeing. You will however see increased usage of other cores for things like passive mob pathfinding if you chuck a bunch of cows on lower half slabs.
Everything below are just my assumptions
Java is heavily dependent on the famous "tick". This is that a tick processes a whole bunch of the world, and then moves onto the next tick. I suspect Bedrock, to keep the same feel, had to do something very similar which has them using a single thread for the main game. Where possible they've spun off behaviours not dependent on game ticks (like path finding as an example).
But you can imagine, if Redstone was completely seperated from the main game processing, things could go horribly awry with all sorts of contraptions.
In either case, this unfortunately doesn't meet the criteria for a bug. Best of luck