s-expressions are OK, but the database could be smaller if they were encoded by e.g. using an integer instead of the spelled-out type-name. Additional compression is possible, but at some point, the cpu-time of additional compression/decompression outweighs storage savings. Note also RocksDB has built-in compression, so this idea is kind-of questionable anyway?
s-expressions are OK, but the database could be smaller if they were encoded by e.g. using an integer instead of the spelled-out type-name. Additional compression is possible, but at some point, the cpu-time of additional compression/decompression outweighs storage savings. Note also RocksDB has built-in compression, so this idea is kind-of questionable anyway?