Hi shankykurella, There is no easy answer to general questions. You have to learn the behaviour yourself, by reading the documentation of the thread group and by experimenting yourself.
There are several options on how to run a test that impact your solution - In Test Plan Gui: "Run Thread Groups consecutively" - In the Thread Group GUI: "Number of threads", "Ramp-up" and "Loop Count" - application under test response times - the timers that you use in the test plan As others said and as you may find on older discussion, all threads run in paralel (depending on the variables above) and their actions synchronize (somehow, depending on how you configure the test plan). Each loop of a thread runs (obviously) after the previous loop ended and this is consecutive and also completely unrelated to the state of the other threads or how many loops they executed. To control this, it depends strictly on you, how you design the test script. Its an endless discussion. You understand this by experimenting yourself. Regards, Adrian On Mon, Nov 7, 2011 at 11:40 AM, shankykurella <[email protected]>wrote: > deicool the count i mentioned as 100 is just a rough count > > and with what you said i can conclude that jmeter is running sequentially > and parallel.... > > because i was asked to check a set of queries simultaneously > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/does-jmeter-runs-in-sequential-or-simultaneously-tp4970264p4970705.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
