Job execution time on qpu

[cosenal]

Some benchmark definitions (e.g. CLOPS) are based off execution time of a job on the qpu. For cloud-accessible platforms, it's important that this metrics is exposed via API. For these benchmarks, the clock can't be taken client-side, o/w it would include queueing time and wire time.

[cosenal]

Some documentation of execution-time like properties for different providers

IBM

job.metadata()
ExecutionSpans

IonQ

job.metadata()
{..., 'start': 1738019212, 'response': 1738019213, 'execution_time': 823, ...}

AWS

Both job.metadata() and job.result() only contain createdAt and endedAt timestamp, but no "startedAt". Since createdAt includes queueing time, it's not useful for CLOPs-like metrics

job.metadata()
{..., 'createdAt': datetime.datetime(2025, 2, 23, 16, 39, 27, 828000, tzinfo=tzutc()), 'endedAt': datetime.datetime(2025, 2, 23, 16, 39, 32, 50000, tzinfo=tzutc()), ...}

Azure

job.result()
Result(...
creation_time='2025-02-25T15:28:30.30961Z',
  begin_execution_time='2025-02-25T15:28:33.814Z',
  end_execution_time='2025-02-25T15:28:33.829Z',
...
)