Hello M. Pepperdine, There is no way today to do that. There is an enhancement request that has not been implemented yet although started some time ago:
- https://issues.apache.org/bugzilla/show_bug.cgi?id=47886 JMeter core is build around the paradigm: - 1 user == 1 Thread - And lot of its internal behaviour makes this supposition This could be changed in 2 ways: - 1) use for example a ThreadPoolExecutor without limiting its growth to avoid thread starvation during a Load Test but to create as little threads as possible - 2) Use a completely different approach based on something like netty but this one would be a revolution and a too big impact in my opinion But even with 1) we have to handle the ThreadLocal objects currently used so this need through investigation. Regards Philippe M. http://www.ubik-ingenierie.com On Tue, Jun 12, 2012 at 6:28 PM, Shmuel Krakower <[email protected]> wrote: > Hi, > I was thinking to suggest working with JP@GC Ultimate thread group, but it > behaves the same (pre-creating the threads). > Kirk, why does it matter to you? > > Regards, > Shmuel. > > On Tue, Jun 12, 2012 at 6:31 PM, Kirk Pepperdine > <[email protected]>wrote: > > > Hi, > > > > I guess this is mostly directed towards Sebb.. I spent a bit looking at > > JMeter performance today. What I found was that the thread group starts > all > > of it's threads at the beginning and then uses them over time. Is there a > > way to easily change this so that the thread group only creates threads > on > > demand? > > > > Regards, > > Kirk > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- Cordialement. Philippe Mouawad.
