Data Compression On Source
Saving storage capacity, speeding up file transfer, and decreasing costs for storage hardware and network bandwidth are all the benefits that compression brings once you set your backup plan. And, GitProtect.io uses compression by default on each backup plan you create.
Considering its customers' needs, GitProtect.io permits you to manage compression settings within your backup plan (advanced settings). You can select the algorithm and the compression level, or dismiss compression settings at all if you don’t need them (everything to meet your needs and expectations!).
So, once you set your backup plan for your DevOps environment (GitLab, GitHub, Bitbucket, Azure DevOps, or Jira) you have two compression algorithm options - LZ4 and ZStandard.
LZ4 compression algorithm
Selecting this option, you get a lossless streaming compression algorithm that is focused on fast compression and decompression speed. So. you get a fast backup compression with a reasonable ratio.
ZStandard compression algorithm
Another option is ZStandard, which is a real-time lossless data compression algorithm that provides a high compression ratio. As it’s backed up by an extremely fast decoder, this compression algorithm offers a very wide range of speed and compression trade-offs.
Compression levels - why to consider?
When it comes to compression levels Gitprotect.io provides, you may choose between:
- Normal, which is characterized as a much faster backup, but it takes more space in your storage
- Medium, which is the most optimal data compression level, as it finds a balance between the time of the compression process performance and the size of the data that occupies your storage space
- High, which may take longer to compress your data, yet it greatly reduces the backup size and saves storage space.