This recording was saved by an earlier build: its steps do not say how many of their occurrences were actually
timed, so the step statistics below are of unknown coverage. Steps whose cost came out negative - the sign of a
never-timed occurrence counted as a duration - are shown as not timed.
Step timings are the time each step spent in its own work - never the time its sub-steps spent in theirs -
summed over every occurrence of that step across all the executions above. Because no step counts another
step's time, these rows add up to at most the Engine total and never more. A step whose whole job is to
dispatch to its sub-steps has no work of its own to time, so it appears with a Count but with no timings.
Step
Count
Measured
Total (ms)
Min (ms)
Avg (ms)
Max (ms)
P99 (ms)
Click Start to begin recording queries from all protocols.
All SQL, Cypher, Gremlin, and other queries will be captured with execution plans and timing data.