11-12-2016, 10:41 PM
So that means having multiple cuberite instances reading and writing to the same "chunk" of "RAM" wouldn't fix these kind of issues? I see redis worked well helping load balance massive 2d multiplayer games, but then none of these were Minecraft.
What if a master-slave approach is used? The master cuberite instance would deal with things that can't be done asynchronously, like redstone processing. Each master-slave task could be assigned to a different server. Lets say I have server a, server b and sever c. Server a would take care of redstone processing, server b would manage entities etc.
This is more of a multi-threading issue than a clustering issue.
What if a master-slave approach is used? The master cuberite instance would deal with things that can't be done asynchronously, like redstone processing. Each master-slave task could be assigned to a different server. Lets say I have server a, server b and sever c. Server a would take care of redstone processing, server b would manage entities etc.
This is more of a multi-threading issue than a clustering issue.