Addition of ExecuteThread executor for running packets.
This commit is contained in:
@@ -11,13 +11,13 @@ ClientReadPoolSize = 100
|
||||
|
||||
# Client pool size for sending server packets.
|
||||
# Each pool is executed on a separate thread.
|
||||
# Default: 50
|
||||
ClientSendPoolSize = 50
|
||||
# Default: 100
|
||||
ClientSendPoolSize = 100
|
||||
|
||||
# Client pool size for executing client packets.
|
||||
# Each pool is executed on a separate thread.
|
||||
# Default: 50
|
||||
ClientExecutePoolSize = 50
|
||||
# Default: 100
|
||||
ClientExecutePoolSize = 100
|
||||
|
||||
# Expected client packet count queued by the server.
|
||||
# Default: 80
|
||||
|
||||
@@ -134,12 +134,6 @@ ScheduledThreadPoolSize = -1
|
||||
# If set to -1, this will be determined by available processors multiplied by 2.
|
||||
InstantThreadPoolSize = -1
|
||||
|
||||
# Use threads to run client packets individually.
|
||||
# Less lag when using threads, but more CPU consumption.
|
||||
# Can try disabling it when server is highly populated and CPU is high.
|
||||
# Default: True
|
||||
ThreadsForClientPackets = True
|
||||
|
||||
# Use threads to decrease startup time.
|
||||
# Default: False
|
||||
ThreadsForLoading = False
|
||||
|
||||
Reference in New Issue
Block a user