1) Threads (in your case 4000) run in parallel . Within a thread everything (the 10 requests) run sequentially. So thread 1 to 4000 will all start at the same time (no ramp up) and make HTTPrequest1 . Lets say Thread1 returns the response then it will move on to the next request and each thread will do the same. however since your server response time will vary , different threads might be on different requests or processing responses.
2) " If many samples exist for the same timestamp, the mean value is displayed." -- http://jmeter.apache.org/usermanual/component_reference.html#Response_Time_Graph It depends on how many threads are executing the request at the same time - its unlikely there are 4000 3) Use a synchronizing timer -- http://jmeter.apache.org/usermanual/component_reference.html#Synchronizing_Timer On Mon, Apr 8, 2013 at 3:01 PM, Bruno Casarotti <[email protected]>wrote: > Hi guys! > I'm new to the list, so I'm sorry if I made some mistake when sending this > email, but let me know to don't do it again ;) > > So, I want to know how does it graph works? > > Let's imagine that I have a single Thread Group with 4000 users, and my > Ramp-Up is 0 and also my loop count is setted for forever. > > I also have 10 HTTP Requests to this Thread Group. > > Question 1) When I run the test, will I run 4000 request per HTTP Request > at the same time? Am I running 40.000 threads at the same time in this > scenario? > > Question 2)My Time Graph is showing to me the avarage response time of 4000 > requests for each HTTP Request? > > Question 3) I need to run 4000 requests for an HTTP link, and after that > more 4000 request for another one and so on, there is some way to do it at > once? I mean, 4000 per time. >
