Just noticed this reading some stuff in the best practices section: http://jmeter.apache.org/usermanual/best-practices.html#jsr223
"For intensive load testing, the recommended scripting language is one whose ScriptingEngine implements the Compilable interface. Groovy scripting engine implements Compilable. However neither Beanshell nor Javascript do so as of release date of JMeter 2.13, so it is recommended to avoid them for *intensive* load testing." I'm curious what "intensive" should be generally interpreted as: * when you see/know the jmeter machines being loaded on CPU and/or memory? * at some typical X requests/sec throughput? * CPU/computationally expensive operations/calculations? (on the jmeter side that is, not the SUT) * network or disk I/O expensive operations? (on the jmeter side that is, not the SUT) * attempting to test very low latency operations? on the order of X ms or ns, etc., thus should equate to high throughput (if sustainable) Some elaboration or examples might be helpful. It's kind of vague to your average user. We can only assume, and assuming isn't always good. I get the feeling beanshell and javascript are more popular with jmeter use than groovy but I could be wrong.
