For meaningful timings, one needs to ensure that a test runs long enough to ensure that any startup overheads are insignificant compared with the length of the test. In general, a single loop won't run long enough to achieve this.
But of course this depends on the content of the test plan, and what you are trying to achieve with the test. If you are not particularly interested in timings, only success/failure of the samples, then the length of the test is not particularly important. Another factor is concurrence - if you want to ensure that all 25 threads are running at the same time, then it is important that the ramp-up time and loop count are selected appropriately. For example: + thread count of 10 + ramp-up of 20 + loop count 1 If the loop takes less than 2 seconds, then each thread will finish before the next one starts, and the number of concurrent threads will be at most 1 throughout the test. On 12/09/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thanks Sebb. Using Jmeter 2.2 i can very well see which requests belong to which thread?But i didnt understand what you said here "A loop count of 1 won't in general produce repeatable results. This is more of a burst test, and the startup overheads are likely to be the major factor in any timings." Can you please elaborate on it a little further. Regards, Subhrajyoti Mobile: +919830079545 Mail: [EMAIL PROTECTED] Web: www.labware.com LabWare LIMS Solutions - Results Count sebb <[EMAIL PROTECTED]> 09/12/2006 05:28 PM Please respond to "JMeter Users List" <[email protected]> To "JMeter Users List" <[email protected]> cc Subject Re: Which requests belong to which thread? A loop count of 1 won't in general produce repeatable results. This is more of a burst test, and the startup overheads are likely to be the major factor in any timings. Having said that, JMeter 2.2 includes the thread name in the View Tree Listener (Sampler Result Pane) and the View Table Listener (Thread Name column) On 12/09/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > I am running a test with about 25 threads and a ramp up period of 25 > seconds and loop count=1. Now my test configuration is such that when ever > there is an error in a particular thread that thread should stop. When I > run the test i see that out of 25 threads some 3-4 threads are stopping > intermittently because of some error. (Seen that from jmeter.log)Now > obviously I know which threads have stopped. But since I am using a View > Tree Listener i have no way to say which request belongs to which thread. > All through out my test i have used Regular expression extractors to parse > the response and put values dynamically into subsequent requests. My gut > feeling is that the threads are failing because responses werent parsed > correctly for a particular thread. Now is there any way to see which > requests belong to which thread?A the monent all the requests are coming > one after another and we cant differntiate between requests from different > threads.Also at the same time i would like to requests and responses like > i am able to do now through View results Tree listener. > > Regards, > > Subhrajyoti > Mobile: +919830079545 > Mail: [EMAIL PROTECTED] > Web: www.labware.com > > LabWare LIMS Solutions - Results Count > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
