I'm also looking into asynchronous/parallel requests. Without it, the load to the server is artificially smoothed out by JMeter test. For example, the browser sends 5 AJAX requests to retrieve a user's items. If JMeter test sends the 5 requests in serial, the server will never be hit by 5 concurrent requests for the same user session and some concurrency problem may be missed.
Regards, Wanjun Wang From: sebb <seb...@gmail.com> To: dev@jmeter.apache.org Date: 05/28/2016 07:31 AM Subject: Re: Reason behind asynchronous sampler Note that as far as the server is concerned, for many (most?) applications it does not matter whether the requests are generated by a single JMeter thread running requests in parallel or multiple JMeter threads. If JMeter generates the same request rate, the server will be stressed in a similar way. On 28 May 2016 at 08:01, harsh patel <h.rs...@gmail.com> wrote: > Hi Philippe, > > Thanks for reply. sure I will try to contribute in this scenario. > > On Sat, May 28, 2016 at 12:08 PM, Philippe Mouawad < > philippe.moua...@gmail.com> wrote: > >> Hello, >> The reason is just lack of time and other priorities. >> As always, contributions are welcome. >> >> Regards >> >> >> On Saturday, May 28, 2016, harsh patel <h.rs...@gmail.com> wrote: >> >> > Hi, >> > >> > I would like to know the philosophy behind not providing parallel >> execution >> > of sampler or controller in thread group. >> > >> > I want to know this because I need controller which execute in parallel >> > with other controller. I know JMeter provide sampler to execute script >> > which can server the purpose. But in this case I need to write whole code >> > in script. Instead If JMeter provide asynchronous controller then i need >> to >> > write code for sampler only. >> > >> > >> > Please let me know the reason so that I can process further accordingly >> > >> > -- >> > Thanks & Regards >> > Harsh Patel >> > 9016696319 >> > >> >> >> -- >> Cordialement. >> Philippe Mouawad. >> > > > > -- > Thanks & Regards > Harsh Patel > 9016696319
