Simplify iozone call and also measure sequential reads #12
Conversation
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
Execution time slightly increases but this will allow in the future to get a bigger picture about the difference the fio measurement with 4 concurrent jobs (quite unrealistic for anything anyone will be doing ever on an SBC) and one single job makes especially in situations where cpufreq governors are used that will quickly ramp up CPU clockspeeds with 4 jobs in parallel but remain on low clockspeeds with iozone (and real-world workloads).
|
I like seeing the live output, so I'll merge then drop the extra bits. I just like having it output while it's doing the test so I can verify things aren't locked up. I'm sure you know how often that can happen on some of the weaker boards :) |
geerlingguy
added a commit
that referenced
this pull request
Apr 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Execution time slightly increases but this will allow in the future to get a bigger picture about the difference the fio measurement with 4 concurrent jobs (quite unrealistic for anything anyone will be doing ever on an SBC) and one single job makes especially in situations where cpufreq governors are used that will quickly ramp up CPU clockspeeds with 4 jobs in parallel but remain on low clockspeeds with iozone (and real-world workloads).
The
| cut -c7-78 | tail -n6 | head -n4can be deleted if the whole iozone output is wanted and not just the results in proper Markdown format.