On 07/10/2008, Joakim D. <[EMAIL PROTECTED]> wrote: > > Hi, > > I have 2 thread groups in my testplan. > The first one adds one item to a web page on the server. That item is > controlled by a variable name declared in csv file. > So each time this thread group is executed a new item is added to the web > page. > > The second thread group justs browse to this page again with a number of > users = 100, ramp up period is 1 second and loop is 0.
Loop count = 0 does not make sense. Also, ramp up of 1 second for 100 users is rather small. Are you really expecting 100 users to access the page at the same time and do nothing else? Timings are best averaged over many loops. > What I want to do is, every time an item is added, 100 users logon to the > server and browse to the webpage. And so on untill 1000 items are added. > This way i can check the delay to browse to this page each time an item is > added. Do you really want to run 1000 tests? Why not run tests with just a few different numbers of items, e.g. 1,100,500,1000. I will soon become obvious if there is a critical point where the number of items starts to have an effect. > Whats the best way to do this? I would probably use two separate JMeter test plans; one to set up the items, and another to measure the response times. But if you really want to use one plan, and you really want to test each number from 1 to 1000, then I think the only way to do it is to use a single thread group: Thread Group (threads = 100) + If Controller (thread number == 1) + + set up item + Test Action + + Synchronising Timer (100) + loop controller + + test pages The Test Action ensures that the item has been added before any other threads continue. > thanks, > Joakim > > -- > View this message in context: > http://www.nabble.com/Problem-with-running-multiple-threads-tp19855081p19855081.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
