Different response time between Silk Performer 17.5 and Chrome developer's tools
Now we are going on a project of getting the response time of a https website, our steps are as following
1. recording the script
2. run 200 virtual users on login transaction in 5 minutes(without using GlobalWaitFor)
3. login one user manually when 200 virtual users run
And we have got the result as following:
1. the response time got by Silk Performer is ~50 second
2. the response time got by Chrome Developer's tools' is ~5 second
We think the respones time got by Chrome is the real time, because we can open the website quickly when 200 virtual
users run. But we don't what the problem is, why the response time got by Silk is so long?
Thanks very much!
RE: Different response time between Silk Performer 17.5 and Chrome developer's tools
Its not possible to answer this question with the information provided. In general you need to know exactly what is being timed in each instance to be able to determine if it makes sense to compare them. Based on this question being asked many times before it is usually the case that you are not comparing like for like.
If you want to open a support case an engineer can look at your scripts and see what might be the cause of the longer perceived timers.