This has been discussed in various forms.

Short answer - This cant be done out of the box in JMeter.

Side question - Does your application actually need this ?
If the two parallel requests the browser makes are fairly independent (i.e.
they dont really lock the same resources or query the same rows any more
than two queries from different users) and the session footprint is also
small then for e.g. if on the average two concurrent requests are made for a
single user , than you should get reasonably accurate results by just
doubling the number of threads
i.e. simply calculate how many requests per second your server should see
and use an appropriate number threads. Each of the 35 tiles will be
requested sequentially by the thread (but have more threads than the number
of users you are testing for)

Longer answer. In theory you might be able to implement this with a bit of
bean shell code . Lets say you want to simulate two requests in parallel.
Then if you wanted to test out 10 users you need 20 threads where Thread 1
and 2 represent user1 , Thread 3 and 4 represent user 2 etc. All even number
threads are only used to simulate the parallel downloads.
You would need some sort of setup to get the session id and share it between
threads (either property or file).
You would need a synchronizing timer (or some such technique) to coordinate
between the threads
For other samplers which do not need this parallel download you need to
check and do something like even numbered threads shouldnt execute
You would need to process the result to calculate the times
There might be other issues too based on your test script.
All in all , it would be complicated and its rarely worth it.

You might also try other tools like Selenium Grid.

regards
deepak


On Mon, Nov 15, 2010 at 3:35 PM, ee <[email protected]> wrote:

> Could someone please comment on the original question?
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to