Skip to content
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

Record job start time obtained via clock_gettime to fix time pain points #1617

Closed
wants to merge 1 commit into from

Commits on Aug 24, 2023

  1. Record job start time obtained via clock_gettime to fix time pain points

    Add a new key in the json per-job output, clock_gettime_job_start, that
    records the job start time obtained via a call to clock_gettime using
    the clock_id specified by the clock_id option. This allows times of fio
    jobs and log entries to be compared/ordered against each other and
    against other system events recorded against the same clock_id.
    
    Rename the alternate_epoch_clock_id option to clock_id, as now this
    clock_id serves two purposes. The primary purpose is to be the clock_id
    for recording clock_gettime_job_start. The secondary purpose is to be
    the clock_id used if log_alternate_epoch is specified, in which case
    each log file timestamp is based on the epoch specified by clock_id.
    (Each such timestamp is obtained by taking the traditional zero-based
    timestamps and adding clock_gettime_job_start to them.)
    
    We also make log_unix_epoch an official alias of log_alternate_epoch,
    instead of maintaining both redundant options.
    
    Fixes axboe#1544
    
    Signed-off-by: Nick Neumann nick@pcpartpicker.com
    aggieNick02 committed Aug 24, 2023
    Configuration menu
    Copy the full SHA
    99dcf32 View commit details
    Browse the repository at this point in the history