This is an advanced topic. If you are not comfortable with making these settings, do not attempt this. Contact GlobalSCAPE Support for assistance.
For more information, review the topics in the Index and Table of Contents to the left. If they are hidden, click <--Show Navigation Pane.
|
This is an advanced topic. If you are not comfortable with making these settings, do not attempt this. Contact GlobalSCAPE Support for assistance. |
In many cases, the Agent and Server are connected via the Internet. In such a connection, bandwidth savings is a prime concern. Because of that, all traffic between the Agent and the Server is compressed, and transfers only byte-level changes.
Essentially, compression is a trade-off of CPU time for bandwidth. Even when both the Agent and the Server are on a LAN, it might still make sense to compress data. This is especially true if both the Server and the Agent are relatively fast computers, and the network is relatively limited.
You might want to disable Agent/Server compression in the following instances:
The Agent and Server are on the same LAN, and either or both are very loaded. In this case, the extra CPU cycles required to compress the transfer might not be worth it. In other words, the cycles for compression are more valuable than transfer savings.
The Agent and the Server are cohosted on the same computer. In this case, compression does not improve performance.
The vast majority of the data transferred between the Server and the Agent is already compressed, such as with most multimedia files.
When you disable one Agent's compression, the communications between it and the Server are not compressed. This setting does not affect the communication compression of the same Server with any other Agents.
To disable or enable compression on an Agent
Download and unzip AvaillCompress.zip.
To disable compression, execute noCompress.reg.
To enable compression, execute Compress.reg.