Open topic with navigation

TIBCO Rendezvous® 8.7.0

# Bandwidth Contention

Bandwidth contention is the second reason to separate programs using disjoint routes.

Consider two programs that are deployed on the same physical network—a program `S2` that sends messages at a moderate data rate, and a program `S1` that sends messages at a relatively high data rate. However, messages from `S2` are much more important to the enterprise as a whole than messages from `S1`.

When forwarding these messages across a WAN, routing daemons would ordinarily send them across the same TCP connection. The many unimportant messages from `S1` could delay the more important messages from `S2`.

To solve this throughput problem, configure an independent route for each set of messages, as in Independent Routing Table Entries Keep Subject Spaces Separate. On the left side of Independent Routing Table Entries Keep Subject Spaces Separate, `S1` and `S2` use distinct UDP services within the same physical network, effectively separating their messages into two logical network spaces. Disjoint routes carry the two sets of messages:

| • | Important messages from `S2` travel through routing entries `A` and `F`.

| • | Messages from `S1` travel through routing entries `B` and `G`.

The heavy volume on this route does not interfere with crucial message throughput on the `S2` route, because a separate TCP connection carries each route.

Did you find this helpful?

Yes No
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 Rendezvous®

Copyright © 1997-2023. Cloud Software Group, Inc. All Rights Reserved.