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
Right now, chunk unloading is done quite aggressively: if it's not a spawn chunk, once a chunk has been left by a player the chunk is queued for unload.
This is pretty bad as it puts pressure on the chunk provider (and by extension causes sync I/O). While async chunk loading allows the server to cope better with this, the current situation is not ideal. At the very least the I/O should be offloaded to the existing I/O thread pool.
The text was updated successfully, but these errors were encountered:
Right now, chunk unloading is done quite aggressively: if it's not a spawn chunk, once a chunk has been left by a player the chunk is queued for unload.
This is pretty bad as it puts pressure on the chunk provider (and by extension causes sync I/O). While async chunk loading allows the server to cope better with this, the current situation is not ideal. At the very least the I/O should be offloaded to the existing I/O thread pool.
The text was updated successfully, but these errors were encountered: