• Iustin Pop's avatar
    Add a new opcode timestamp field · b9b5abcb
    Iustin Pop authored
    
    
    Since the current start_timestamp opcode attribute refers to the inital
    start time, before locks are acquired, it's not useful to determine the
    actual execution order of two opcodes/jobs competing for the same lock.
    
    This patch adds a new field, exec_timestamp, that is updated when the
    opcode moves from OP_STATUS_WAITLOCK to OP_STATUS_RUNNING, thus allowing
    a clear view of the execution history. The new field is visible in the
    job output via the 'opexec' field.
    Signed-off-by: default avatarIustin Pop <iustin@google.com>
    Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
    b9b5abcb
jqueue.py 42.1 KB