I discovered that the 'elapsed' value of each job is the overall time the whole fio run took, not the per-job elapsed time, despite it being in the per-job section of the json output. Rather than break everybody by fixing this, just add a 'job_runtime' value to the job section and include the time the thread ran in milliseconds. This is handy for jobs that want to compare runtime of two threads in different cgroups. Signed-off-by: Josef Bacik <josef@xxxxxxxxxxxxxx> --- v1->v2: - use 'job_runtime' instead of 'total_run_time' stat.c | 1 + 1 file changed, 1 insertion(+) diff --git a/stat.c b/stat.c index d5240d96a25b..a308eb884557 100644 --- a/stat.c +++ b/stat.c @@ -1288,6 +1288,7 @@ static struct json_object *show_thread_status_json(struct thread_stat *ts, usr_cpu = 0; sys_cpu = 0; } + json_object_add_value_int(root, "job_runtime", ts->total_run_time); json_object_add_value_float(root, "usr_cpu", usr_cpu); json_object_add_value_float(root, "sys_cpu", sys_cpu); json_object_add_value_int(root, "ctx", ts->ctx); -- 2.14.3 -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
