If compression is required this service can be enabled. This will reduce the required storage size especially for archives where documents are archived which can be compressed easily like plain text, xml, json or cat files. Lesser reasonable it is if binary files are archived. Pay attention that compression requires calculation power and time. Archiving and retrieving data from archive can be more time consuming and the required hardware may enforded.

Requirements

There are no special requirements for using the compression service. Only configuration of the service is necessary. The service can be configured individually for repositories. Only the included compression algorithms can be used: gzip, bzip2.

If not configured, no compression takes place.

The compression service can be enabled at any time. Any existing, uncompressed files are still accessible.

The compression service can also be disabled at any time. Any existing compressed files are still accessible.

Configuration

The compression service is addressed via the repository (here using the CE repository as an example).

Depending on the used algorithm, the size of the original file changes, i.e. a different content length appears on the storage system.