evitaDB icon indicating copy to clipboard operation
evitaDB copied to clipboard

Support compression / decompression of the storage records

Open novoj opened this issue 1 year ago • 0 comments

We should consider and write performance tests for the situation when the stored records in the key/value store are decompressed. For example, one of the promising Java libraries is: https://github.com/airlift/aircompressor/tree/master

Pros:

  • Data will be smaller and thus there would be less I/O disk requests
  • backup/file requirements will be smaller
  • Binary entities will cost less to transfer over the wire to the client side (probably, since there is also compression at the HTTP/2 level)

Disadvantages

  • There will be a performance penalty associated with both compression and decompression of the data.

The compression should be optional and the compressed records should be marked by a specific bit of control byte.

novoj avatar Jan 11 '24 19:01 novoj