Getting different response time from WebLOAD (Performance testing tool) to Dynatrace
Hi,
We are getting different response time from WebLOAD (Performance testing tool) to Dynatrace.
Please clarify us in letting know that exactly what is the response time in Dynatrace.
The response time in WebLOAD means : The time it takes the ABT to send the object of an HTTP request back to a virtual client, in seconds. In other words, the time from the end of the HTTP request until the virtual client has received the complete item it requested.
The value posted in the Current Value column is the average time it took the ABT to respond to an HTTP request during the last reporting interval.
The response time for one transaction i.e. “get Profile” using WebLOAD is Response Time : 3530 sec
The response time for one transaction i.e. “get Profile” using Dynatrace is Response Time : 848 sec
Please find the attached document for screenshots
Request you to kindly let us know why was there difference in response time.
Thanks,
Sandhya
Hi
First I would recommend checking out the following recorded webinar: dynaLearn Webinar - Load Testing Made Easy with dynaTrace 4.2 - August 1, 2012
As for Response Times. dynaTrace captures the response time on the Server Side whereas WebLoad measures it from their "load producing machines". So - there is a natural difference because they will see the full Response Time including the network, ...
Then - depending on the Load Testing Tool they may show you the "total page load time" - which means it is the time it takes to download the initial HTML + Images + JavaScript + CSS and present it all under one name, e.g: "get Profile", dynaTrace on the other side will see each individual Web Request that is executed. That could be 1 or 100 for a single "Page". Therefore the "average" response time that dynaTrace will show you is total time it took to execute all these requests that you have marked/tagged with that dynaTrace HTTP Header divided by the number of requests there were.
If in your case you really only have one web request executed for your "get Profile" then the explanation would be that there is something between the Load Robot and the App Server (thats where dynaTrace picks up the PurePath) that is responsible for that difference. That could be network, load balancers, web servers, ...
I hope this makes sense
