Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# RTC Options — Single-Threaded or Concurrent

Depending on your needs, you can choose single threaded or concurrent RTC options, in the CDD Agent settings Concurrent RTC field.

For reference documentation, see TIBCO BusinessEvents Developer Guide.

## Concurrent RTC

In the option Concurrent RTC, one RTC executes simultaneously on each thread.

All threads fill post RTC queues. As with any concurrency feature, locking is required.

Figure 19: Concurrent RTC

Advantages | Disadvantages
--- | ---
Can confer performance benefits, given correctly sized hardware and JVM configuration. Best on large high-capacity, high-performance machines. Does not require cache or store OM. | When many smaller CPUs are used, then concurrent agents may give better performance than concurrent RTC. Requires the same kind of locking as for multi-agent concurrency to protect integrity of the data. The cost of locking negates some of the performance benefits of concurrency. If you also use concurrent agents, the system can become complex.

## Single-Threaded RTC

In the option Single-Threaded RTC, each thread waits to execute its RTC in turn.

Figure 20: Single-Threaded RTC

Advantages | Disadvantages
--- | ---
It's simpler and does not require locking (unless concurrent agents are used). | Lesser performance than concurrent RTC (depending on hardware used).

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.