Shared Queue

All destinations that use the shared queue threading model share the processing unit’s shared queue and threads.

The default and most straightforward option is when one pool of worker threads picks jobs from the shared queue. Execution continues on a thread through to post-RTC.

Shared Queue

The configuration settings are as follows:

Property Notes
CDD Editor > Collections > Destinations > Threading Model: Shared Queue
  Specifies that the shared queue threading model is used.
CDD Editor > Agents > Queue Size
  Specifies the size of the queue used for all destinations in the processing unit that use the shared queue threading model.
CDD Editor > Agents > Thread count
  Specifies the number of threads used for all destinations in the processing unit that use the shared queue threading model.
Advantages Disadvantages
  • Good for multi-core machines, which can make good use of a heavily threaded set-up.
  • Too many threads create context switching.
  • One single destination can become a bottleneck in the case of a sudden increase in incoming messages.
  • Correlation of events arriving on different queues at different rates can be problematic, as can request-reply situations.
  • It can be harder to tune performance with only one queue and one set of threads for all destinations.