You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the threads created from the owner thread pool, optional physics engine parallelism and hytale server's concurr in cpu cores budget and latency.
To avoid this the proposed solution is assign specific cores to the physics engines and (optionally) to the threadpool.
From my research the most threads usage in hytale server is from world generation. The legacy world generation (ChunkGenerator) doesn't have a limit on the conccurent thread usage and it uses a euristic max(2, ceil(n_threads * 0.75)) formula. While worldgen v2 (HytaleGenerator) supports CustomConcurrency settings by overriding Server/HytaleGenerator/Settings/Settings.json .
At the moment the threads created from the owner thread pool, optional physics engine parallelism and hytale server's concurr in cpu cores budget and latency.
To avoid this the proposed solution is assign specific cores to the physics engines and (optionally) to the threadpool.
From my research the most threads usage in hytale server is from world generation. The legacy world generation (ChunkGenerator) doesn't have a limit on the conccurent thread usage and it uses a euristic max(2, ceil(n_threads * 0.75)) formula. While worldgen v2 (HytaleGenerator) supports CustomConcurrency settings by overriding
Server/HytaleGenerator/Settings/Settings.json.