Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# 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.

Figure 12: 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.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.