Data Compression | |
| |
Data Compression Over Network
Data are sent over the network between the NativeApps_3DEXP Client and FCS server. If the network is experiencing poor performance, data will be impacted.
To reduce the impact of the network, data can be compressed to reduce its size prior to being transferred over the network. If the network bandwidth is experiencing poor performance, and if the power of the processors allows it, we recommend that you compress the data.
In the following example, the WAN between Native_Apps Velizy (France) and the server Pune (India) has poor latency and bandwidth, whereas the LAN between Native_Apps Velizy (France) and the server Velizy (France) has high performance:
Consequently, for a data size of 250 MB, a very rough estimation of the elapsed data transfer time without data compression:
- At best 2 s between Native_Apps Velizy (France) and the server Velizy (France)
- At best 4,167 s between Native_Apps Velizy (France) and the server Pune (India)
which naturally encourages you to compress the data being transferred between Velizy (France) and Pune (India).
The following diagram illustrates succinctly where the compression and uncompression
components are located:
- Activate Compression
- The files sent to the FCS server will be compressed if the setting “Activate FCS Upload Compression” is activated (CheckIn).
- The files downloaded from FCS server will be compressed if the setting “Activate FCS Download Compression” is activated (CheckOut).
Whichever option you choose, your choice is stored in your user settings (in the CATPLMxNetwork.CATSetting file), so that data compression optimization can be applied at logon.