Forum Discussion
sbeauvais
11 years agoContributor
Hello.
I appreciate your help, but the fix is apparently for a proxy issue, and I'm not using a proxy.
I have just tried my tests on SoapUI Pro 4.6.4 (x64), and the behaviour is the same:
- the TestCase Log shows that each DataGen took on average 5 ms per row (with the odd higher value)
- the TestCase Log shows that each PUT request took on average 50 ms per row
- the TestCase Log shows that each DataSource loop took on average 2 ms per row (with the odd higher value)
- during execution, I could see a 1/2 second delay between rows
- the entire TestCase (44 rows) took "2358" (I don't know what this is... a sum of all the delays in ms?)
- the SoapUI log shows that the "first attempt to execute the request" occurred at 08:52:29
- the SoapUI log shows about 1/2 second between each "Stale connection check" and the next "attempt to execute request"
- the SoapUI log shows the final "Connection can be kept alive" at 08:52:50, for a total of 21 seconds, which is about 1/2 second per row
From this, it still looks like each request is taking on average 50-60 ms per row, but there is a still huge delay somewhere.
Cheers,
Severin B.
I appreciate your help, but the fix is apparently for a proxy issue, and I'm not using a proxy.
I have just tried my tests on SoapUI Pro 4.6.4 (x64), and the behaviour is the same:
- the TestCase Log shows that each DataGen took on average 5 ms per row (with the odd higher value)
- the TestCase Log shows that each PUT request took on average 50 ms per row
- the TestCase Log shows that each DataSource loop took on average 2 ms per row (with the odd higher value)
- during execution, I could see a 1/2 second delay between rows
- the entire TestCase (44 rows) took "2358" (I don't know what this is... a sum of all the delays in ms?)
- the SoapUI log shows that the "first attempt to execute the request" occurred at 08:52:29
- the SoapUI log shows about 1/2 second between each "Stale connection check" and the next "attempt to execute request"
- the SoapUI log shows the final "Connection can be kept alive" at 08:52:50, for a total of 21 seconds, which is about 1/2 second per row
From this, it still looks like each request is taking on average 50-60 ms per row, but there is a still huge delay somewhere.
Cheers,
Severin B.
Related Content
Recent Discussions
- 5 days agogroovyguy