TTM Network Administration Documentation
- What’s New In This Release
- TTM Overview
- Unicast And Multicast Network Communication
- Network Setup And Configuration
- Installing And Upgrading TTM And Guardian
- TTM Daemon
TTM Remote Host Daemon And Remote Clients
- Introduction to the TTM Remote Host Daemon
- Remote Mode: Pros and Cons
- Remote Mode Operations
- Network Considerations when Deploying the Remote Host Daemon
- Configuring a Remote Host Daemon
- Configuring the Remote Client
- Compressing Data
- Manually Configuring TCP Window Size
- Testing the Remote Connection
- Remote Host Daemon Failover (Disaster Recovery)
- Advanced Topics
- Maintenance And Troubleshooting
- Ttmd.cfg File Reference
Remote Mode: Pros and Cons
Advantages to Using Remote Mode
Using remote mode to connect to a trading network has the following advantages:
- You can easily set up end-users.
- You can customize your distribution by presetting remote mode configurations.
- You can configure failover, such that should one Remote Host Daemon fail, TTM automatically attempts to connect to a designated backup Remote Host Daemon.
- Remote mode works well with nodes that:
- Receive a dynamic IP address
- Reside behind a transparent Network Address Translating (NAT) or Port Address Translating (PAT) device, otherwise referred to as NAT with overloading
- Communicate through a firewall to reach the host machine
- You need to open only one port (by default this is 10200), when using a firewall to restrict outbound connections.
- You do not need to configure and support IP multicast in the network infrastructure between segments connected via a Remote Host Daemon.
- Remote Host Daemons are more efficient at hosting large numbers of Remote Clients than WAN Routers are at hosting large numbers of WAN Routing peers.
Disadvantages to Using Remote Mode
Remote mode can be bandwidth intensive. Whenever the Remote Host Daemon sends data to multiple instances of Remote Client applications, it sends the same data once for each application connected to it. Thus, if ten clients subscribe to the same information, the Remote Host Daemon sends the same data ten times (using ten times the amount of bandwidth that IP multicast forwarding does). However, you can minimize bandwidth usage by configuring the Remote Host Daemon to compress data before sending it over the network (for details on TTM’s compression, refer to Compression).
For further details on bandwidth usage, refer to Bandwidth Considerations.
Because Remote Clients perform better with more bandwidth, at minimum TT recommends you use a broadband connection to remotely access the Remote Host Daemon.
Even if order, fill, and price updates are sent to and from Remote Clients in compressed packets of data, the following actions by traders can negatively affect performance depending on the amount of available bandwidth:
- Subscribing to 20 or more rows in the Market Grid.
- Subscribing to Market Depth for more than one product at a time.
- Subscribing to detailed Market Depth.
If you encounter performance issues when connecting to multiple exchanges or downloading fills, you must either:
- Increase the bandwidth of your remote connection
- Decrease your network demands (i.e., subscribe to less products or disconnect from an exchange)
Remote users with broadband connections experience no limitations.
The best way to improve the performance of a Remote Client is to obtain a higher bandwidth connection to the Internet such as through a cable, DSL, or other leased line connection. These sorts of connections can minimize or eliminate the problems listed above.
Do not use remote mode connections in a LAN environment. Doing so can lead to severe degradation in performance. Instead, connect normally.