Set file buffer size to optimize file transfer rate

If you find that the transfer of large files is sluggish, you can optimize the file transfer rate by adding the following buffer parameters to the fcc.properties file: buffSize Sets the internal buffer size which is used to read data from the file system and the segment caches. For peak I/O efficiency, this value should always be a multiple of 16KB and also always a multiple of the file system sector size. Following is the commented text for this parameter in the fcc.properties.template file: Copy # FCC internal buffer size. # Default value is 64K. # Value should be in 16K increments. # Minimum is 16K. # (The setting name you see here is correct; this information is internally # associated with the FMS server cache (FSC) connections.) # #com.teamcenter.fms.servercache.FSCConstants.buffSize=64K sockBuffSize Controls the Transmission Control Protocol (TCP) window size in the Java TCP stack, which is used for reading and writing data from network connections. This size must exceed the BDP (bandwidth delay product) of the network connection in order to prevent acknowledgment (ACK) response throttling caused by the TCP window filling with unacknowledged data. To calculate the BDP of a network connection, multiply the round-trip latency (seconds) by the network bandwidth (bytes per second). A factor of about 2:1 is needed for reliable high-performance operation. Following is the commented text for this parameter in the fcc.properties.template file: Copy # Socket buffer size override. # Default value is (com.teamcenter.fms.servercache.FSCConstants.buffSize * 2) + 1024. # The value 0 disables setting the socket buffer sizes (uses system default). # Minimum value is 8K (excluding the 0 case). # (The setting name you see here is correct; this information is internally # associated with the FMS server cache (FSC) connections.) # #com.teamcenter.fms.servercache.FSCConstants.sockBuffSize=129K Tip To add these parameters to the fcc.properties file, open the fcc.properties file in the FMS_HOME directory. Copy the parameter to the file and remove the comment character (#) from the line containing the parameter. If the fcc.properties file does not exist, copy the fcc.properties.template file to the FMS_HOME directory and rename it as fcc.properties. The buffSize and sockBuffSize parameters can also appear in the fsc.properties file, the fsc.clientagent.properties file, or the fscadmin.properties.template file. When determining the socket buffer size, use the largest BDP of all of the other FMS modules (FSCs and FCCs) to which this FMS module connects. For example, an FSC server that connects to clients over a BDP=600MB LAN and other FSCs over a BDP=100KB WAN should use the 600MB LAN value to determine the socket buffer size. The socket buffer size is typically set to twice the internal buffer size plus a little more. This is reflected in the default value. The internal buffer size should be a little less than half of the socket buffer size, but nonetheless, a convenient multiple of the local disk sector size. This value should definitely never be more than the socket buffer size. The minimum socket buffer size should be determined by the local hard disk rather than the network connection (which functions correctly when the TCP window size is too big). Consider this example: Round-trip latency = 750ms Bandwidth = 400 Mbits/sec BDP = 750ms * (400 Mbits/sec) * (1 sec/1000 ms) * (1 byte/10 bits) = 300000 / 10000 = 30 MBytes If the BDP is 30 MBytes, make the socket buffer size a little larger, and the socket buffer size roughly half of that. But 15 MB (half of the BDP) is not a multiple of the hard disk sector size (4MB in this hypothetical case), so make the internal buffer size 16 MB. This makes the socket buffer size about (twice 16 is 32 MB, plus a little more), or say, 33 MB. Note For the byte/bits setting, allow 10 bits per byte to account for 8 data bits plus start/stop bits on network media.