On 15/12/05, Bill Herndon <[EMAIL PROTECTED]> wrote: > Sebb, > > Thanks for the response. > > Two reasons for doing it this way. First, built in constraints on the > number of users that can authenticate concurrently causes some Jmeter > threads to get failure results from the server. These threads then > proceed to attempt the test requests that then also fail, corrupting the > test. Second, the authentication sequence sometimes takes so long that > it seriously biases the test results, even when all test requests are > successful. > > Basically I'm trying to control for these two issues by only > authenticating once.
But surely the test is then not properly representative? If you set a suitable ramp-up time, it should be possible to ensure that the authentication requests don't occur together. Then just repeat the subsequent tests sufficiently often so that the threads overlap. Or you can add a synchronising timer. The Once Only controller is useful for the login. Or you can do something like: Thread Group, count = 1 + Loop Controller, count = 1 + + Login + Loop Controller, count = n + + Sampler 1 + + Sampler 2 If you choose suitable names for the samplers, the Aggregate Listener will accumulate the samples accordingly, allowing you to show the login time separately --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
