Response time mismatch in User Action purepath
Hi Team,
We have observed that server time around 700 ms but when we expand that User Action purepath then one of component taking more than 4000 ms .
Please find attached snapshot.
Please help me.
Regards,
Jalpesh Shelar
Response Time is the time perceived by the end user - so - it is the time we capture from start to end of the action. It DOES NOT include server-side asynchronous activity as this does not impact the end users response time / user experience
Hi Reinhard ,
It's showing total response time as 1276 ms,but one of request taking 4 seconds.
Does total response time including asynchronous processing time or not?
Regards,
Jalpesh Shelar
Response time is the rendering the user experiences. If you have a asynchronous call (e.g. some timer action) it can of course be smaller than the other (timed) actions.
Well, if the serverside Execution of this specific request takes 700ms but on the client side (the User Action) plus any asynchronous processing takes 4 seconds then this could mean:
a) the transfer of the data responded by the server takes a significant time (network time)
b) there is client side processing of the data returned that takes 4s to complete
You can check the request/response size in the details of that request, or if you suspect extensive processing on the client side use a browser agent to analyze javascript execution.
Reinhard
Hi Jalpesh, Reinhard,
Very useful insights, actually I have a similar scenario, but since I'm a bit "obsessive" some times, I was sitting there in front of the browser, and experienced that the user had actually to wait for over 40 seconds (in my example) to "notice/experience" anything on his side:
https://community.compuwareapm.com/community/pages/viewpage.action?pageId=186524017
Our customer can actually look at the purepath / web request + context info, and dig deeper on the 45 seconds.
But if you look at the Visits, or User Actions dashboards/perspective, it is a bit misleading, in my humble opinion of course.
Thanks for reading through,
Carlos.
