This is a bug in the command-line tool.
I changed (somewhat) the algorithm for caching source-data blocks, in order
to support streaming source files. You aren't using a streaming source, so
this should not have happened. I'll fix ASAP.
For now, you can raise -B. See if giving it another 10% solves the
problem. If that works, it'll mean there's a boundary condition error
somewhere. If you run with three or four -v's it will print source-block
evictions as they happen, you'll notice quickly.
I'll address this two ways: (1) print a warning when the source-I/O is
performing badly (suggesting to raise -B), (2) the encoder/decoder should
not become source-I/O-bound when they use the same -B setting, I'll add a
test to verify this.
Original issue reported on code.google.com by josh.mac...@gmail.com on 7 Nov 2009 at 2:55