On 2 February 2011 12:03, tsv <tsvetomir.ma...@consol.de> wrote: > > "Why x 3? > Surely you only want 2 Thread Groups, the second with only one thread? " > > after your suggestion I must create 3 thread groups a user because I have 3 > (not 2 as mentioned I the original post) request types with different delay > time (2.5 min, 3min and 10 min). >
I uinderstood the front-end controller (3 min schedule) to be a single source, so only a single thread. That's why I suggested a parallel thread group. If the same users are doing different kinds of requests every few minutes, then you should be able to use an If Controller with a condition derved from the time. > "but it's extremely unlikely that you > need to run so many threads.." > > I must simulate up to 6000 users (customer want that) load on the server. Load is not the same as users. As I already wrote, a JMeter thread can generate a much larger load than a human user. Decide what load the server needs to see in terms of requests. Then build the test plan and adjust timers / loop count to generate the required load *as measured at the server*. > Every user has all types of requests. Means I have if I understand right > 6000 x 3 threads running on my machine. The machine which is running the > JMeter is server it self, so I have a bit more hardware resources on it too. Even 6000 threads is rather a lot for a single node. > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Time-counters-tp3367557p3367674.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
