I've some remarks regarding the tests and the test data in this survey.<p>- The data used in the benchmark seems very compressible. However floating point data (also time series) is in general not well losslessly compressible and the Gorilla algorithm is not helping so much.<p>- TurboPFor Integer Compression [1] has also an improved and faster Gorilla algorithm TurboGorilla (not shown in the benchmark)<p>- TurboPFor has now a new lz based algorithm "TurboFloat LzX" witch drastically compress time series floating point data (up to 3 times).<p>- TurboPFor supports lossy compression [2] (TurboRazor) with a point wise relative error bound. The preprocessed data can be further compressed with any floating point compression algorithm.<p>- TurboPFor supports floating point conversion to integers. The result data can be compressed with any integer compression algorithm.<p>You can test all this functionality with icapp, a TurboPFor benchmark app. Download the excutable for windows + linux from [3]<p>See also the time series floating point benchmark [4] "TurboFor: Time Series" showing different szenarios, using 32-bits instead of 64-bits floating point data like in the benchmark above.<p>[1] <a href="https://github.com/powturbo/TurboPFor-Integer-Compression">https://github.com/powturbo/TurboPFor-Integer-Compression</a><p>[2] <a href="https://github.com/powturbo/TurboPFor-Integer-Compression/issues/94">https://github.com/powturbo/TurboPFor-Integer-Compression/is...</a><p>[3] <a href="https://github.com/powturbo/TurboPFor-Integer-Compression/releases">https://github.com/powturbo/TurboPFor-Integer-Compression/re...</a><p>[4] <a href="https://github.com/powturbo/TurboPFor-Integer-Compression/issues/95">https://github.com/powturbo/TurboPFor-Integer-Compression/is...</a>