Hi sebb, Thanks for your comments. I actually didn't know that JMeter uses blocking HTTP requests. I have heard that Netty can handle more concurrent non blocking connections than blocking connections. (I will try to find some reference links later).
My only concern is that load average of the JMeter server is very high. Have you monitored load average while running a test? On Mon, Sep 11, 2017 at 1:22 PM, sebb <seb...@gmail.com> wrote: > On 11 September 2017 at 07:26, Isuru Perera <chrishan...@gmail.com> wrote: > > Hi Philippe, > > > > I'm sorry for not explaining my reasons sooner. > > > > So, the main reason for asking about a Netty Client Implementation for > HTTP > > Sampler is that Netty is supposed to be better at working under large > > number of concurrent non blocking connections. > > Better than what? > > Note also that JMeter uses blocking HTTP requests. > It is not currently designed to use asynchronous HTTP requests. > > > The main issues we are having with current HTTP Sampler are: > > > > 1. Load Average of the JMeter instance is very high. See thread: > > http://www.jmeter-archive.org/Maximum-number-of-concurrent- > > users-td5726006.html > > <http://www.jmeter-archive.org/Maximum-number-of- > concurrent-users-td5726006.html>. > > Even for low number of concurrent users (eg, 300), if there is no > timers > > added to the test plan, the load average of the client goes beyond > > acceptable limits. > > 2. With the default value for "httpclient4.time_to_live", we see very > > high response times. When we increase the time_to_live value for 30 > minutes > > to keep a fixed number of connections, the response times are much > better. > > See also > > http://www.jmeter-archive.org/Number-of-open-connections- > vary-with-time-tp5726000p5726123.html > > > > I'm wondering whether we could avoid above issues with a Netty Client > > Implementation instead of the default client implementation in JMeter. > > > > WDYT? > > > > Thank you. > > > > On Tue, Jul 25, 2017 at 10:44 AM, Isuru Perera <is...@apache.org> wrote: > > > >> Hi Philippe, > >> > >> I'm sorry about the delay. I'll send a mail explaining the reasons soon. > >> > >> On Fri, Jul 21, 2017 at 12:30 AM, Philippe Mouawad < > >> philippe.moua...@gmail.com> wrote: > >> > >>> Hello, > >>> Why do you want that ? > >>> Thanks > >>> > >>> On Thu, Jul 20, 2017 at 3:35 PM, Isuru Perera <is...@apache.org> > wrote: > >>> > >>> > Hi all, > >>> > > >>> > I found a Netty client implementation for HTTP2: > >>> > https://github.com/syucream/jmeter-http2-plugin. However, I couldn't > >>> find > >>> > a > >>> > Netty client implementation for HTTP Sampler. > >>> > > >>> > On Wed, Jul 19, 2017 at 3:32 PM, Isuru Perera <is...@apache.org> > wrote: > >>> > > >>> > > Hi Devs, > >>> > > > >>> > > Is there a Netty client implementation for HTTP Sampler either > using > >>> > Netty > >>> > > directly or using https://github.com/AsyncHttpCl > >>> ient/async-http-client? > >>> > > > >>> > > -- > >>> > > Isuru Perera > >>> > > about.me/chrishantha > >>> > > > >>> > > >>> > > >>> > > >>> > -- > >>> > Isuru Perera > >>> > about.me/chrishantha > >>> > > >>> > >>> > >>> > >>> -- > >>> Cordialement. > >>> Philippe Mouawad. > >>> > >> > >> > >> > >> -- > >> Isuru Perera > >> about.me/chrishantha > >> > > > > > > > > -- > > Isuru Perera > > about.me/chrishantha > -- Isuru Perera about.me/chrishantha
