Compression options

[Mike Donovan]

Both Dbvisit and SSH use zlib compression, but it is our experience that 'on the fly' SSH compression often takes a lot more CPU cycles than Dbvisit internal compression.

So, if you are looking for the most CPU effective method, we would recommend trying the Dbvisit compression. Alternatively you can also use gzip or other external compression - whatever is available on your particular server.

As part of your testing procedures we would also suggest switching off the compression to get an idea of how much overhead the compression is taking in terms of CPU processing, if that is an area of concern.

[Mike Donovan]

Generally speaking compression is a CPU intensive operation.

Compression of the archive logs is an option that is provided for those instances where Dbvisit installations have bandwidth restrictions. If this is not the case then it may in fact make more sense to turn compression of the archive logs off.