zvault/chunking
Dawid Ciężarkiewicz c8874829a1 bench: Don't drop the output data
Since in the current benchmarks the output data is discarded, compiler
is smart enough to eliminate all data copying (both in to the buffer,
and out of the buffer), and roll over the original buffer only.

With this change the overhead of coping things is being measured as
well. I still wonder if both copyings are being done, or just the one
out of the buffer.

In the real code, at least the out of the buffer copying would be
unavoidable, as unless something can be done immediately with that data,
it has to be copied somewhere, eg. to send for processing to another
thread.
2017-08-06 00:45:53 -07:00
..
benches bench: Don't drop the output data 2017-08-06 00:45:53 -07:00
src More tests, forcing cut-point-skipping, using black_box 2017-08-03 07:34:16 +02:00
tests More tests, forcing cut-point-skipping, using black_box 2017-08-03 07:34:16 +02:00
Cargo.lock Added fixed chunker 2017-04-19 19:54:53 +02:00
Cargo.toml Moved chunker to separate crate (re #17) 2017-04-19 17:35:25 +02:00