How to interpret the duration of the purepath when it refers to multiple executions of the same SQL query? Is this the duration of all requests or the duration of a single request? In this case the purepath is the consequence of a consolidation because the queries were executed one after the other or because the pattern of the query was identified several times during the execution of the purepath?
The duration of the PurePath from start to end.
It is the wall-clock time (difference between start and end time), not the sum of all asynchronous executions.
Have a look at the below link for more insight.
Thanks for your answer but I don't think you saw the attached photo which refers to my question. May be the question is not precise enough it concerns SQL part of the purepath.
You are right. I did not notice the shared link by you. This is the response time of all SQL executions. At the code level, the duration can also explain client-side response time for these executions.