Displaying 5 results from an estimated 5 matches for "zlib9".
Did you mean:
zlib
2015 May 10
3
Packet compression benchmark
...18.98 MB/s, ratio 0.53 23.82 MB/s, ratio 1.01
zlib7: 56.38 MB/s, ratio 0.01 24.95 MB/s, ratio 0.42 18.54 MB/s, ratio 0.53 23.81 MB/s, ratio 1.01
zlib8: 56.31 MB/s, ratio 0.01 24.78 MB/s, ratio 0.42 17.67 MB/s, ratio 0.53 23.82 MB/s, ratio 1.01
zlib9: 56.23 MB/s, ratio 0.01 24.77 MB/s, ratio 0.42 17.64 MB/s, ratio 0.53 23.82 MB/s, ratio 1.01
lzo1x_1: 960.53 MB/s, ratio 0.03 262.21 MB/s, ratio 0.60 265.83 MB/s, ratio 0.68 1153.17 MB/s, ratio 1.01
lzo1x_999: 92.66 MB/s, ratio 0.01 22.01 MB/s, ratio 0....
2018 Aug 02
2
Default compression level for -compress-debug-info=zlib?
...SD it
could be a CPU bottleneck? Though we should also bear in mind that
compression can be pipelined with writes in i) and debug info loading could
be lazy in ii)
(e.g. for highly compressible data we've generally seen ~10MiB/s output
bandwidth on single thread i7 @3.2GHz memory to memory for zlib9 with 32KiB
window, that doesn't stack up well against modern IO)
How is the compression implemented in lld? Is it chunked and therefore
paralellizable (and able to be pipelined with IO) or more serial?
I think the intention is i) so we'd be happy to link a few of our game
titles with vary...
2018 Aug 02
3
Default compression level for -compress-debug-info=zlib?
...hould also bear in mind that
>> compression can be pipelined with writes in i) and debug info loading could
>> be lazy in ii)
>>
>> (e.g. for highly compressible data we've generally seen ~10MiB/s output
>> bandwidth on single thread i7 @3.2GHz memory to memory for zlib9 with 32KiB
>> window, that doesn't stack up well against modern IO)
>>
>> How is the compression implemented in lld? Is it chunked and therefore
>> paralellizable (and able to be pipelined with IO) or more serial?
>>
>> I think the intention is i) so we'd...
2018 Aug 02
3
Default compression level for -compress-debug-info=zlib?
...;> compression can be pipelined with writes in i) and debug info loading could
>>>> be lazy in ii)
>>>>
>>>> (e.g. for highly compressible data we've generally seen ~10MiB/s output
>>>> bandwidth on single thread i7 @3.2GHz memory to memory for zlib9 with 32KiB
>>>> window, that doesn't stack up well against modern IO)
>>>>
>>>> How is the compression implemented in lld? Is it chunked and therefore
>>>> paralellizable (and able to be pipelined with IO) or more serial?
>>>>
>>...
2018 Aug 02
2
Default compression level for -compress-debug-info=zlib?
Also not an expert, but would it make sense for this to be configurable at
a fine-grained level, perhaps with another option, or an extension to the
compress-debug-sections switch interface? That way users who care about the
finer details can configure it themselves. And we should pick sensible
options for the default.
James
On 2 August 2018 at 11:08, Pavel Labath via llvm-dev <
llvm-dev at