Add option to send different randomized blocks #1907
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version of iperf3 (or development branch, such as
master
or3.1-STABLE
) to which this pull request applies:master
Issues fixed (if any): iperf3: use incompressible data for streaming test #1871
Brief description of code changes (suitable for use as a commit message):
Add a second option to
-l
to specify number of different (randomized) blocks to send. The purpose is that not all sent blocks will be the same, and as the blocks contents is randomized by default, network compression will not have an effect.Test, that stored the received data for 1KB blocks into a file, shows that when sending the same block contents, zip of the file achieves more than 99% compression. On the other hand, when the block contents repeats only every 100 blocks, zip achieves almost no compression.
The change includes also initializing a stream buffer only when it is a sending stream.