Description
This is to investigate uncompressing speedup: the block-boundaries aware implementation seems to pass through a file twice: once to find the block boundaries, to produce the slices, and then again block-by-block. The first pass seems also rather slow, with per byte bit fiddling, plus single-threaded. Which is also non-cancelable.
We might also need to implement here a fallback mechanism that trades in memory for speed.
Description
This is to investigate uncompressing speedup: the block-boundaries aware implementation seems to pass through a file twice: once to find the block boundaries, to produce the slices, and then again block-by-block. The first pass seems also rather slow, with per byte bit fiddling, plus single-threaded. Which is also non-cancelable.
We might also need to implement here a fallback mechanism that trades in memory for speed.