PlayerCulling

To limit the amount of resources PlayerCulling can use, see the thread limit in the plugin configuration. By default it limits itself to (number of CPU threads / 3).

Here are some examples on how the PlayerCulling scheduler works. The following examples were tested on an arch linux desktop environment with an AMD Ryzen 5 3600X CPU:

• One Container

  One container is able to handle the load of 42 players without many problems.
  
  
• Two Containers

  If the load increases, the scheduler will automatically create a second container and distribute the players to maintain a buffer. In this example, a total of 55 players are together in an area.
  
  
• Cleanup of Containers

  If a container is no longer used because the load decreased, it gets parked first. After its time-to-live (TTL) runs out because the load didn't increase again, it will get cleaned up automatically.
  
  
• Heavy Load

  The scheduling system is theoretically able to scale to an infinite amount of containers. As long as the load increases (and the limit of containers hasn't been reached yet), the scheduler will automatically continue to add more containers. In this example, a total of 112 players are together in an area.
  
  
• Merging of Containers

  If the load of multiple containers is too low, they will be merged together after a few seconds.
  
  

The first bossbar shows info about the container with the highest load and general container scheduling statistics:

• The count of Running containers
• The count of Parked containers
• The count of total container Threads
• The count of total Raysteps per cull tick

The second bossbar shows the load of the occlusion world cache, the working threads, amount of Completed tasks, amount of Stored chunks and the chunk cache size in bytes.

The third bossbar shows info about culled players. The maximum amount of culled players can be calculated by (playercount) * (playercount - 1).

In this example, a total of 112 players are together in an area. The server was running in an arch linux desktop environment with an AMD Ryzen 5 3600X CPU.