fio - keep numjob always under 256 #3137
Merged
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
In fio test, numjob*max_iodepth (aio-nr) should always be less than aio-max-nr. The default value of aio-max-nr is 65536. As max_iodepth is 256, numjob which is equal to 'nproc' should not exceed 256. /proc/sys/fs/aio-nr is the number of events currently active. /proc/sys/fs/aio-max-nr is the maximum number of events that can be queued. If aio-nr reaches aio-max-nr the io performance will drop and io_setup will fail with EAGAIN. read: https://www.kernel.org/doc/Documentation/sysctl/fs.txt So we set numjob to 256 if numjob is larger than 256.
SRIKKANTH
force-pushed
the
smyakam/storage_perf_aio_max_nr
branch
from
f311d9d
to
eb2a865
Compare
LiliDeng
reviewed
Jan 15, 2024
LiliDeng
approved these changes
Jan 30, 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.
No description provided.