Contributions
Re: [Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Update: Curiousity got the better of me and I installed the latest nightly build (2009-09-11-[2]). I have run and re-run my script with and without the offending groovy-script test step. The metrics I now see are consistent between the two versions of soapUI. So, it looks like whatever you fixed last night has cured the problem. I am going to stick with this latest build until such time as the next formal release of soapUI 3.0 becomes available. Thanks for your help and efforts. Sean857Views0likes0CommentsRe: [Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Hi Ole, When running my script, I get the average execution time by running a load test (simple strategy, 10 threads, test delay 1000, 60s duration). Upon completion of the test I am reporting the test case average from the "avg" column in the load test table. So, whatever is included in this metric is what I am reporting. When comparing soapUI 2.5 beta 1 results against v.3.0.1 results I am using the same metric, so I am comparing like with like, which indicates an issue to me. The evidence that leads me to suggest that it is related to groovy script execution is the large time difference when using the two versions of the same stock script - one with 100 hard coded number values, the other with 100 random groovy-script-generated random number values. Appreciate your ongoing investigations here. Is it worth my time installing the nightly build or do you think the issue requires more investigation/fixing? Thanks, Sean857Views0likes0CommentsRe: [Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Update: I think it is related to the execution of Groovy script in v.3.0.1. I cloned the offending web request and replaced the 100 instances of groovy script with hard-coded values. I then disabled the original web request and enabled the clone. When I ran this script in 2.5 beta 1 and 3.0.1 I get similar average times in the load test (c.300ms). When I revert to the oiginal web request I then get c.300ms in 2.5 beta 1 but nearer 8,000ms in 3.0.1. I think this may be related to the way 3.0.1 executes groovy script on the fly during a script execution - has there been a change here since 2.5 beta1? Thanks Sean859Views0likes0CommentsRe: [Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Hello Robert, I ran load tests on both the tests included in the sample project file you sent me. I ran these in both versions 2.5 beta 1 and 3.0.1. Like you, I get similar results, in the order of 140ms. I then tried cloning the test steps to give multiple steps in each test on a hunch that perhaps chained test steps might be a causal factor. This wasn't the case and the timings were again similar. I also tried including multiple 209.85.129.104 calls (with different values) within the < getgeoip=""> method. Once again, the timings were similar. I went back to my original test script and ran it again in both versions. I still see the significant timing difference. Delving deeper into the individual test steps in my script I see that one web request in particular is contrubuting to the timing difference. I am going to send you a private message with a copy of the 'offending' web request. I am wondering if the fact that it contains 100 separate groovy scripts might be a factor. Just a thought. Perhaps you could review this call and give me your thoughts? Thanks Sean1.9KViews0likes0CommentsRe: [Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Hi again Ole, The results below are for repeated runs of the same functional test script. soapUI 2.5 beta1 (ms) #1: 2,351 #2: 189 #3: 169 #4: 171 #5: 161 #6: 203 #7: 163 #8: 191 #9: 194 #10: 188 soapUI 3.0.1 (ms) #1: 5,142 #2: 1,258 #3: 1,512 #4: 1,554 #5: 2,663 #6: 1,506 #7: 1,200 #8: 1,626 #9: 1,199 #10: 1,617 The results are consistent and still appear to point to significant differences between the soapUI versions.1.9KViews0likes0CommentsRe: [Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Hi Ole, Running a function test with the same base script in both version of soapUI I get: -- in soapUI 2.5 beta1, execution time = 982ms -- in soapUI 3.0.1, execution time = 4,125ms Interestingly enough, I then tried replicating the same calls using our application. I ran Fiddler2 to inspect the timings of the resulting web service calls. I measured each discrete request/response to the server and added up the times. I got 542ms, which is closer to the soapUI 2.5 beta 1 results, which I feel are closer to the actual experience through our application.1.9KViews0likes0Comments[Resolved]Response time differences between soapUI 2.5 beta1 and soapUI 3.0.1
Hi, I have been running a load test in soapUI 2.5 beta1 and have now upgraded to soapUI 3.0.1. My colleague and I have both noticed that there is a huge difference in the response times now recorded when executing a test. We are using the same test script, using the same HTTP settings in 'Preferences', using the same load test parameters on the same target software on the same test environment; in short the only thing different is the version of soapUI used. How can this be? I would appreciate any helpful comments. The set of results (in milliseconds) below helps illustrate the problem when running a simple load test with 10 virtual users for a 60s period: soapUI 2.5 beta 1 min: 147 max: 6865 avg: 376.1 cnt: 511 bytes: 15,704,167 soapUI 3.0.1 min: 4983 max: 24222 avg: 12821 cnt: 46 bytes: 1,413,8645.1KViews0likes16CommentsRe: How to transfer a dynamic property to subsequent test steps?
Hi Ole, Many thanks for your quick reply. I tried your suggestion and it worked. I inserted a Groovy Script as the first test step, called "Set the username", with just the one line of script to initialise and define the 'dynamic' username value to be persisted down through all the test steps as follows : def myusername = "MySoapUITester" + (int)(Math.random()*10) I then modified the property transfer test step before the test requets step to move myusername, setting the Source = "Set the username" and Property = "Result" and setting the Target as normal to my test request step's request property. Thanks again. Sean926Views0likes0Comments