...
Given below are a list of tuning parameters related to threading:
| Table of Contents |
|---|
| maxLevel | 4 |
|---|
| minLevel | 4 |
|---|
| type | flat |
|---|
|
flusherPoolSize
| Parameter | <flusherPoolSize> |
|---|
| Description | This is the thread pool size which will be used by the Sender Task to send messages asynchronously to the subscriber for Queue Messages. You will have to consider the value of the <messageBatchSizeForSubscribers> parameter and the number of local queue subscriptions for the node when configuring this pool size. |
...
|
| Example | | Code Block |
|---|
<flusherPoolSize>10</flusherPoolSize> |
|
subscriptionPoolSize
| Parameter | <subscriptionPoolSize> |
|---|
| Description | WSO2 MB has |
...
| an "In Order Message Delivery Mechanism Across Broker Cluster". This coordinates messages one by one, hence it is very slow. This configuration is for configuring the pool size of the thread pool to submit message delivery threads. If there are a lot of subscriptions to the system at a given instance, |
...
...
number with the <OnceInOrderSupportEnabled> parameter set to true. ( |
...
| This mode of operation is discouraged because of the slowness of message delivery due to coordination across clusters for each message |
...
...
|
| Example | | Code Block |
|---|
<subscriptionPoolSize>20</subscriptionPoolSize> |
|
internalSequentialThreadPoolSize
| Parameter | <internalSequentialThreadPoolSize> |
|---|
| Description | When message content and metadata is written to Cassandra storage, those jobs are submitted to a thread pool. This configuration is for setting the size for that thread pool. If TPS of incoming messages are high, consider increasing this thread pool size for fast acceptance of incoming messages to be written to Cassandra storage. |
| Example | |
...
<internalSequentialThreadPoolSize>5</internalSequentialThreadPoolSize> |
|
andesInternalParallelThreadPoolSize
| Parameter | <andesInternalParallelThreadPoolSize> |
|---|
| Description | This is the thread pool size which will be used by the Andes core to schedule its internal parallel tasks such as acknowledgement handling and message content writing. Consider increasing for fast message handling in general. |
| Example | |
...
<andesInternalParallelThreadPoolSize>50</andesInternalParallelThreadPoolSize> |
|
publisherPoolSize
| Parameter | <publisherPoolSize> |
|---|
| Description | Both queue messages and topic messages are scheduled to be delivered to local subscriptions of the node using a thread pool of this size. So if there are a lot of subscribers or a lot of messages to be delivered at a given instance, consider increasing this value. |
| Example | | Code Block |
|---|
<publisherPoolSize>50</publisherPoolSize> |
|