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