Chapter 22. Optimizing Data Throughput

Table of Contents
22.1. Binary Mode Tunnel/Mirror (TCP) Connections
22.2. Tunnel/Mirror (TCP) Heartbeat and Timeout
22.3. Old Value Queuing
22.4. Un-Buffered Delivery
22.5. Screen Output
22.6. CPU Saturation
22.7. How to Optimize
22.7.1. Tunnel/Mirror (TCP) connections
22.7.2. DataHub C++ API
22.7.3. Gamma scripts

The Cogent DataHub program has a wide range of configuration options. Among these there are several settings that will optimize data throughput, which are explained in this chapter.

22.1. Binary Mode Tunnel/Mirror (TCP) Connections

TCP/IP connections to a DataHub instance can be either ASCII or binary mode. A large part of the CPU cost of transmission is marshalling messages (constructing messages at the source and parsing them at the destination). The binary mode is more efficient in both network bandwidth and CPU usage for both the sender and the receiver. Binary mode requires that the CPU architecture of the sender and the receiver agree, so you can only use this mode if you are running both the sender and the receiver on an Intel x86 CPU. The CPU gain could be as much as 50% when using binary mode. Numeric data benefits most from this option.

How to Optimize