Connection Throughput Is Too Slow

Symptoms:

• Message throughput does not meet expectations.

• Message input/output rates are not limited by an insufficient number of supported connections (as described in A Client Cannot Establish a Connection).

Possible causes:

• Network connection or WAN is too slow.

• Connection service protocol is inherently slow compared to TCP.

• Connection service protocol is not optimally tuned.

• Messages are so large that they consume too much bandwidth.

• What appears to be slow connection throughput is actually a bottleneck in some other step of the message delivery process.

Possible cause: Network connection or WAN is too slow.

To confirm this cause of the problem:

• Ping the network, to see how long it takes for the ping to return, and consult a network administrator.

• Send and receive messages using local clients and compare the delivery time with that of remote clients (which use a network link).

To resolve the problem: Upgrade the network link.

Possible cause: Connection service protocol is inherently slow compared to _TCP.

For example, SSL-based or HTTP-based protocols are slower than TCP (see Transport Protocols).

To confirm this cause of the problem: If you are using SSL-based or HTTP-based protocols, try using TCP and compare the delivery times.

To resolve the problem: Application requirements usually dictate the protocols being used, so there is little you can do other than attempt to tune the protocol as described in Tuning Transport Protocols.

Possible cause: Connection service protocol is not optimally tuned.

To confirm this cause of the problem: Try tuning the protocol to see whether it makes a difference.

To resolve the problem: Try tuning the protocol, as described in Tuning Transport Protocols.

Possible cause: Messages are so large that they consume too much bandwidth.

To confirm this cause of the problem: Try running your benchmark with smaller-sized messages.

To resolve the problem:

• Have application developers modify the application to use the message compression feature, which is described in the Message Queue Developer’s Guide for Java Clients.

• Use messages as notifications of data to be sent, but move the data using another protocol.

Possible cause: What appears to be slow connection throughput is actually a bottleneck in some other step of the message delivery process.

To confirm this cause of the problem: If what appears to be slow connection throughput cannot be explained by any of the causes above, see Factors Affecting Performance for other possible bottlenecks and check for symptoms associated with the following problems:

• Message Production Is Delayed or Slowed

• Messages Are Backlogged

• Broker Throughput Is Sporadic

To resolve the problem: Follow the problem resolution guidelines provided in the troubleshooting sections listed above.