Exec total [ms] is the total execution time of that node of the PurePath tree and all its child nodes. Elapsed time [ms] you can think of it as a stopwatch, when the PurePath is detected at entry level (web request in your case) we start the stopwatch (thus, the elapsed time is 0). Then the next node shows what the stopwatch would show at that point, and so on until the very last node.
It is normal for the Exec Total to reduce as you go along, because, as you go along, each node has less and less child nodes. If we look at the first 4 nodes of the PurePath:
Does this make sense?
You can also right click on the column title bar, and choose to add more columns. One of the options to add is "Exec [ms]" - this represents the execution time of that particular node, not including its child nodes.
Yes that make sense. Thanks for explaining.
One last question for a single purepath, after the entry point at the second step my elapsed time is 7700 but the overall exec time of that second step is around 6700 (similar to what I had in the screenshot earlier) , to me it seems to be 1000 ms being missed. Is that not the case here?.
Should we expect the numbers to be add up and match the exact ms at the very beginning ?