search for: paralellizable

...d 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 varying compression levels vs storage types and let you know the results. Might be a couple of weeks... > I wonder what is the best compression level when -...

...ble 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 varying compression levels vs storage types and let you know >> the results. Might be a couple of weeks... >> >> &gt...

.../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 varying compression levels vs storage types and let you know >>>> the results. Might be a couple o...

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