-
Notifications
You must be signed in to change notification settings - Fork 166
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Lay out files using fio in the benchmark. (#1108)
## Description of change This makes the benchmarks more self-contained, creating the state that they need to run rather than relying on pre-created state (potentially with different/unknown mount options and/or object properties). It does change behaviour a little: previously the multi-thread tests would use the same object whereas now each thread uses its own object -- arguably this is a more useful test but results in higher S3 usage. Also note that the cache benchmark is unchanged in this commit, because it makes assumptions about the filename used by the tests. Removing the assumption that each test will operate on a single file prepares us for future mixed read/write tests, and allows different fio jobs to be run in parallel safely. ## Does this change impact existing behavior? Yes, see above: previously the multi-thread tests would use the same object whereas now each thread uses its own object -- arguably this is a more useful test but results in higher S3 usage. ## Does this change need a changelog entry in any of the crates? No. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the [Developer Certificate of Origin (DCO)](https://developercertificate.org/). Signed-off-by: Andrew Peace <[email protected]> Signed-off-by: Andy Peace <[email protected]>
- Loading branch information
Showing
5 changed files
with
35 additions
and
43 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1c6f819
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible performance regression was detected for benchmark 'Throughput Benchmark (S3 Standard)'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
2
.random_read_four_threads_direct_io
4.13369140625
MiB/s21.93291015625
MiB/s5.31
random_read_four_threads
4.064453125
MiB/s17.75322265625
MiB/s4.37
random_read_direct_io
0.95556640625
MiB/s3.196875
MiB/s3.35
random_read
1.139453125
MiB/s3.40947265625
MiB/s2.99
This comment was automatically generated by workflow using github-action-benchmark.