Forum Discussion
Sean_Paterson
15 years agoOccasional Contributor
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 multiple209.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
Sean
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
Thanks
Sean
Related Content
- 9 months agoDGISQ