Hardware and Software Requirements - Trading Technologies

More documents

Recommendations

Info

MPF Environment • You can configure your TT trading environment to decouple (i.e., off load) much of the price functionality from several TT Gateways of a particular market onto a separate TT server. • Using MPF2, you can configure one TT Gateway to provide prices to client applications and then configure additional TT Gateways to provide clients with order and fill connectivity. TT Gateways that supply only order and fill data must host a server component called the Price Proxy. • Ensure the Contracts-Per-Message parameter in Aconfig is set to 50 on all TT Gateways and MPF TT Gateways (instead of four (4)). • Price Proxy servers should also have the Contracts-Per-Message parameter set to 50. This is found in the priceproxy.ini file. Note: For more information on setting up an MPF2 environment, contact your local TAM. Globex (CME, CBOT) Adhere to the following best practices when installing Globex Gateways: • TT Globex Gateways should have two or more NICs with one pointing to the internal network and one or more pointing to the CME price distribution feed. • Point MDP to limited channels (i.e., Equity Futures channel). • TT Gateways allow a maximum of 10 channels per TT Gateway. • It is recommended to have separate TT Gateways for specific channel groups. For example, a customer could install a TT CME Gateway dedicated to just NYMEX products (channels) or one dedicated to just EOS products. • Monitor the number of iLink connections per TT CME Gateway for degradation of performance. Consult with your TAM to determine and optimal number of iLink sessions per TT Gateway.
LIFFE Connect Adhere to the following best practices when installing TT LIFFE Connect Gateways: ICE • In a failover group, TT recommends each TT Gateway connect to a unique LIFFE Connect Gateway. Each TT LIFFE Gateway in the failover group should also have the same keys and the same IDs in User Manager. • Keep “prod_at_open” current, especially in a failover environment. This entry is found in the HostInfo.cfg file and is referenced when the TT LIFFE Gateway starts up. • If possible, do not point the software of more than one Independent Software Vendor (ISV) to a single LIFFE Connect Gateway. • One Price server should connect to one LIFFE Connect Gateway (recommended). • Each TT LIFFE Gateway should have its own dedicated price key. Note: Other ISVs do not connect to LIFFE the same way. Some require that each individual trader establishes its own Price API connection. TT has one Price API connection per LIFFE Connect Gateway; all traders connecting to the TT LIFFE Gateway will use this API connection. Adhere to the following best practices when installing ICE Gateways: • Use a direct line to connect to ICE due to security and performance issues with the Internet. • If a customer chooses to use an Internet connection, it is recommended that SSL encryption is used. When using the Internet, install and configure an SSL wrapper like S Tunnel. FMDS Note: When using direct lines, TT does not recommend using SSL encryption as this slightly decreases performance. FMDS servers require a 300 GB or larger hard drive. FIX Adapter FIX Adapter servers require 60 GB or more of available space, per FIX Adapter instance. Autospreader SE Autospreader SE servers require at least an eight core machine, e.g., Dual Quad-Core, or better. Synthetic SE Synthetic SE servers require at least an eight core machine, e.g., Dual Quad-Core, or better.
Page 1 and 2: Hardware and Software Requirements
Page 3 and 4: Hardware and Software Requirements
Page 5 and 6: Server or Product Synthetic SE Reco
Page 7 and 8: Components Network Card Minimum Req
Page 9 and 10: Hardware and Operating System — W
Page 11 and 12: • Wake On = Disable • Wake up M
Page 13 and 14: Power Save Settings To avoid unexpe
Page 15 and 16: Hardware and Operating System — W
Page 17 and 18: NIC Teaming Limited testing perform
Page 19 and 20: Windows Services In Windows Service
Page 21: TT Gateways — Market Data Traffic
Page 25 and 26: TT WAN Router Registry • Add the
Page 27 and 28: X_TRADER Remote Hosts Keep the foll
Page 29 and 30: • Nagling: Enable Nagling by sett
Page 31 and 32: Additional Best Practices for Serve
Page 33 and 34: Client-Class Machine Optimizations
Page 35 and 36: Registry Set “No Arp’ing” by
Page 37 and 38: Windows Performance Settings Ensure
Page 39 and 40: Network Connection Properties TT re
Page 41 and 42: Power Save Settings To avoid unexpe
Page 43 and 44: Windows Performance Settings • En
Page 45 and 46: TT Client-Class Software General Do
Page 47 and 48: Guardian When an Administrator upda
Page 49 and 50: Additional Best Practices for Clien
Page 51 and 52: Appendix: Setting Descriptions NIC
Page 53 and 54: NIC Setting Description Microsoft Q
Page 55 and 56: NIC Setting Transmit Descriptors =
Page 57 and 58: NIC Setting Rx Max Coalesced Frames
Page 59 and 60: Table 1: Registry Setting TT Machin

Hardware and Software Requirements - Trading Technologies

Create successful ePaper yourself

Delete template?

Save as template?