Whether automatic compression of stored data is enabled or not.
Whether checksum is required when storing pre-compressed entries,
for actual uncompressed content. If so, and caller does not provide
checksum, exception will be thrown. Otherwise checksum verification
can not be used.
Name of root directory (using relative or absolute path) under which
data files will be located (possibly with additional dir hierarchy).
Maximum size of entries that are to be stored inline in the database,
instead of written out separately on file system.
Defualt value of about 4k is aligned to typical page size.
Minimum size an entry needs to have before we consider trying to
compress it. Low threshold used since smallest of content will
not compress (due to header overhead etc).
Maximum uncompressed size of payload that will try to use GZIP
encoding; bigger payloads will use LZF due to reduced I/O costs
(and skippability of content).
Goal is to try to gzip inlined entries, use LZF for disk; and
assuming 4-to-1 compression we will use default size of 16k
We will read up to this number of bytes in memory, before switching
to actual streaming handling. Note that streaming content will
never be inlined; and compression choice can not check whether
content is compressible (beyond basic compression prefix checks)