-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fio reports higher runtime than the configured value #1640
Comments
Please try a current version of fio. The latest is 3.35. |
@vincentkfu As far as I understand, the latest version available for Ubuntu 20.04 is 3.16 (https://packages.ubuntu.com/search?keywords=fio). |
@vincentkfu is there any way we can update to fio 3.35 on Ubuntu 20.04 ? |
I installed fio 3.35 by building it from source code in this repo with tag fio-3.35 as @vincentkfu suggested in #1640 (comment) . And then I ran the jobs that @raj-prince shared in #1640 (comment) , but the indiviaul fio job runtimes still overshoot the runtime set in the job file (60 seconds). cat fio-output.json | grep '"runtime"' | grep -v ': 0'
"runtime" : "60s",
"runtime" : 60074,
"runtime" : 64764,
"runtime" : 60173,
"runtime" : 61647,
"runtime" : 60200,
"runtime" : 61768,
"runtime" : 60259,
"runtime" : 61922,
"runtime" : 60139,
"runtime" : 70952,
"runtime" : 60429,
"runtime" : 62345,
"runtime" : 60270,
"runtime" : 62062,
"runtime" : 60373,
"runtime" : 62306, @vincentkfu is this a known issue in fio ? |
You have a heavily loaded system and it takes fio some time to record the timestamp when a job completes. Within each group fio reports the highest runtime as the group runtime. Set |
Thanks @vincentkfu . I'll try out
Could you please expand on this ? Will some runtimes exceed 60s even after setting group_reporting to 0 ? |
On running
|
@vincentkfu is it possible to get the start and end times of individual job-groups (shown in below sample fio job file) if they are are all stonewalled e.g. below?
Currently we are calculating them (start, end times of job-groups) in reverse order by progressively subtracting the the inserted delays i.e. the ramptimes, runtimes, and startDelays from the final timestamp in the fio output. However the total runtime of fio (calculated by |
In the JSON output is a new job start time key that was added via a recent pull request: #1621 Might this help? You will need to update to the tip of the repository to see this feature. |
Please acknowledge the following before creating a ticket
Description of the bug:
Fio reports higher runtime than the configured one
Environment: Ubuntu 20
fio version: fio-3.16
Reproduction steps
Fio job specs - https://github.com/GoogleCloudPlatform/gcsfuse/blob/ce0a93d1ddfe33ae1bfeabff98eba7befab03a9f/perfmetrics/scripts/job_files/seq_rand_read_write.fio
Ouput json:
Here, we can see the runtime for job_name: 2_thread is 85s, but we have configured 60s runtime for every job.
Expectation:
We want to calculate the start and end_time of every configured job. Currently we are calculating the start and end-time using the
runtime
value reported by fio, which is not correct. Could you please help me in calculating the correct start and end-time of the fio job.The text was updated successfully, but these errors were encountered: