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.
This runner skips benchmarks unless it can do them in a single AWS CLI command. If we used multiple commands, one after another, it wouldn't be a fair comparison to the other runners that do everything in parallel. And users probably aren't running multiple CLI commands in parallel, so it doesn't seem worth doing that comparison either.
Here are examples showing how this works:
upload-5GiB
aws s3 cp upload/5GiB/1 s3://graebm-s3-benchmarks/upload/5GiB/1
upload-5GiB-20x
aws s3 cp upload/5GiB s3://graebm-s3-benchmarks/upload/5GiB --recursive
--include
the ones we want:upload-5GiB-10x
aws s3 cp upload/5GiB s3://graebm-s3-benchmarks/upload/5GiB --recursive --exclude "*" --include 1 --include 2 --include 3 --include 4 --include 5 --include 6 --include 7 --include 8 --include 9 --include 10
"filesOnDisk": false
then we upload from stdin, or download to stdout. This only works if the benchmark has 1 file.upload-5GiB-ram
<5GiB_random_data> | aws s3 cp - s3://graebm-s3-benchmarks/upload/5GiB/1
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.