Performance Implications of Using Connection Manager

When connecting to internal servers that require many connections (for example, Internet Server connections to Oracle DB), it is best practice to minimize the number of connections established. Use of MFT Connection Pooling can minimize the number of TCP connections created between Internet Server and the Oracle DB server.

Slight performance degradation also exists when Internet Server uses Connection Manager to send bulk to internal servers. For example, Internet Server often needs to send gigabytes of data to TIBCO MFT Platform Server in the internal network. Instead of sending the data over a single connection, the data needs to be sent over multiple connections (Internet Server-CMA, CMA-CMS, and CMS-Platform Server). Many variables can affect the performance of file transfers using Connection Manager: Client network bandwidth, file size, and latency. At best, negligible performance differences exist between direct connections. Initial tests show approximately 10% - 15% performance degradation when used in a high volume, low latency, and fast network. After connections are made, CMA and CMS just pipes data from the source connection to the target connection and therefore use very little CPU and very little memory. To save CPU cycles, data is piped to the remote destination exactly as sent or received by Internet Server. If you want to encrypt the data, you must configure Internet Server to use secure protocols.