> On Mar 6, 2018, at 1:58 PM, Garreau, Alexandre wrote:
>
> Le 05/03/2018 à 14h54, Mark Adler a écrit :
>> deflate has an inherent latency that accumulates enough data in order
>> to efficiently emit each deflate block. You can deliberately flush
>> (with zlib, not gzip), but if you do that too f
Le 05/03/2018 à 14h54, Mark Adler a écrit :
> deflate has an inherent latency that accumulates enough data in order
> to efficiently emit each deflate block. You can deliberately flush
> (with zlib, not gzip), but if you do that too frequently, e.g. each
> line, then you will get lousy compression
deflate has an inherent latency that accumulates enough data in order to
efficiently emit each deflate block. You can deliberately flush (with zlib, not
gzip), but if you do that too frequently, e.g. each line, then you will get
lousy compression or even expansion.
I wrote something called gzlo
Hi,
I have a script which has a logged very repetitive textual output
(mostly output of ping and date). To minimize disk usage, I thought to
pipe it to gzip -9. Then I realized the log, contrarily to before,
remained empty, and recalled the GNU policy of “reading all input and
only then outputting
