Batch Modes for Transports

In a narrowly limited set of situations, the batch mode for network transport objects feature can improve application performance. Most customers can ignore this feature.

This section presents batch modes that are available only for transports connected to daemons; they do not apply to TIBCO RendezvousÆ Server In-Process Module (IPM).

With default batch behavior, a transport object transmits outbound messages to the Rendezvous communications daemon as soon as possible.

With timer batch behavior, the transport can delay transmitting small outbound messages to the daemon. For programs that send many small messages, this behavior can improve efficiency. The cost of that improvement is data latency.

When used appropriately, it is possible that timer batching can promote one or both of these advantages:

•

In some situations, it can reduce context switching on the sending computer, improving CPU utilization.

•

In some situations, it can reduce the number of packets on the network, improving bandwidth utilization.

These conditions characterize situations where timer batch mode might be advantageous:

•

Maximum data latency of approximately 25 milliseconds is acceptable.

•

The program sends very small messages—generally 100 bytes or fewer.

•

A correct program performs poorly with default batch behavior.

These conditions characterize situations that contraindicate timer batch mode:

•

Increased data latency is not acceptable.

•

Timer batch behavior does not produce measurable improvements in the performance of your application.

Programs control batch mode by setting a property of the transport object.