|Parameter Name||Description||Default Value|
|worker_pool_size_core||Initial number of threads in the worker thread pool. This can be increased to match an increased number of messages to be processed unit the value specified for the |
Maximum number of threads in the worker thread pool. Specifying a maximum limit helps to avoid performance degradation that can occur due to context switching.
Ifyou get the error
the queue (
Maximum period of inactivity between two consecutive data packets. Given in milliseconds.
|worker_thread_keepalive_sec||Defines the |
The keep-alive time in seconds forextra
idle threads in the worker pool. This should be less than the socket timeout
. Once this time has elapsed for anextra
idle thread, it will be destroyed.
The purpose of this parameter is tooptimise
optimize the usage of resources by avoiding wastage that results from havingunutilized extra
|worker_pool_queue_length||Defines the |
The length of the queue that is used to hold runnable tasks to be executed by the worker pool.The thread pool starts queuing jobs when all the existing threads are busy and the pool has reached the maximum number of threads. The value for this parameter should be -1 to use an unbounded queue. If a bound queue is used and the queue gets filled to its capacity, any further attempts to submit jobs will fail causing some messages to be dropped by Synapse
If the number of live threads is equal to the core pool size (
If the queue is full, all threads are busy and the number of live threads is equal to the max pool size (
|io_threads_per_reactor||Defines the number of IO dispatcher threads used per reactor. The value for this property should not exceed the number of cores in the server.|
|io_buffer_size||Size in bytes of the buffer through which data passes.|
|http.max.connection.per.host.port||Defines the maximum number of connections allowed per host port.|
|http.socket.reuseaddr||If this parameter is set to |
This is used to configure the