topic Re: PurePath timing in waterfall vs server side in Real User Monitoring

PurePath timing in waterfall vs server side

Yosi_Neuman — Fri, 19 Jan 2018 17:39:18 GMT

Hi guys,

When looking into the waterfall of a selected instance we can see the time of the PurePath in this case 22s

When drilling into the PurePath there is only 800ms

Also looks odd for me that in waterfall it says at the top that there are 2 PurePaths but only one is aluminate when clinking on it.

Any explanation for this?

Yos

Re: PurePath timing in waterfall vs server side

afzal_qureshi — Tue, 15 Oct 2019 20:59:10 GMT

any answers?

Re: PurePath timing in waterfall vs server side

JamesKitson — Wed, 16 Oct 2019 03:32:30 GMT

The response time of the PurePath which is the server side timing is 800 ms, what you see in the waterfall is how long it took for that request to load from the perspective of the browser which can include network time and processing time within the browser among other things - the timings really never should line up exactly.

If you hover over the request in the browser it will give you some more info on what phase of loading in the browser time was spent.

The note in your image explains why only one can be selected - the other couldn't be tied back to a specific user action.