Hi,

There's many threads on this list about simulating high number of users with
jMeter. The main limitation seems to be the number of threads. I wonder why
jMeter uses the "1 dedicated Thread per (Virtual) User" strategy :

   - each Thread uses native memory, large number of threads requires much
   memory
   - Thread context switch consumes CPU time. Switching hundred of threads
   on few cores over-consumes ressources.

So, my question is : is there any plan, or any previous attempt, to use
thread pools in jMeter ? Typically, beeing based on Java 5,
java.util.concurrent provides the adequate thread pooling tools.

Cheers,
Nicolas

Reply via email to