FileReplicaitonPro does support compression of the replicated data.
Compression is turned on or off in the Advanced settings of each server and affects only the server for which you edit the option. Both servers in any job should be set to the same setting IE: compression enabled or disabled.
Files are compressed prior to transmission with our internal algorithm, transferred and then decompressed on the other end.
This reduces bandwidth and transfer time, at a cost of additional CPU and Memory usage. When the balance of system resources to bandwidth is right it can be a big advantage.
One other factor is the compressibility of the files themselves, some files usually binaries do not compress too well and can cost more in resources than it saves in transfer time.
Some points to remember:
1. Since you are only replicating the changed bits of the file the actual repliation data stream may be so small that compression is a waste of time and resources. You can determine this by observation and experiment.
2. Compression will require more memory and CPU power, depending on your hardware and the number of jobs you are running it could affect overall performance. This can be adjusted for by changing the allowed memory usage for FRP, see the article on increasing Memory for instructions.