Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
MIME-Version: 1.0
In-Reply-To: <1400143180.23146.7.camel@ubuntu>
References: 
 <CAH9fUpYOgA_TatgwF8K2EmzwcL0DSSkUiR0GZ9vVQVEJL9oN5A@mail.gmail.com>
	<1400066881.11226.2.camel@ubuntu>
	<CAOGo0VafyDaofaoDDpGA=nOswCwn8WhOd7-8KLXn53trpNa61w@mail.gmail.com>
	<1400143180.23146.7.camel@ubuntu>
Date: Sun, 20 Dec 2015 22:44:25 +0100
Message-ID: 
 <CAH9fUpbzFiE6EcL1uqg3FuoDFWrDw9p8QnNuYvioMRJ4DCbxaA@mail.gmail.com>
Subject: Re: httpClient.getConnectionManager() performance with HTTP only
From: Philippe Mouawad <philippe.mouawad@gmail.com>
To: "dev@jmeter.apache.org" <dev@jmeter.apache.org>
Cc: HttpClient User Discussion <httpclient-users@hc.apache.org>
Content-Type: multipart/alternative; boundary=047d7bdca2e8b30a4505275b4662

--047d7bdca2e8b30a4505275b4662
Content-Type: text/plain; charset=UTF-8

Hi Oleg,
Back to this old subject and knowing that we must stick to 1 HttpClient per
thread (as per all the discussion that followed this).
Is there a plan to implement this lazy init of SSLContext in HttpClient as
it used to be the case in HC3 ?

For our project, it's a killer in terms of performance, and for other use
cases, it appears kind of weird that an SSLContext is initialized even for
a pure HTTP traffic.

Thanks
Regards


On Thu, May 15, 2014 at 10:39 AM, Oleg Kalnichevski <olegk@apache.org>
wrote:

> On Wed, 2014-05-14 at 19:46 +0100, sebb wrote:
> > On 14 May 2014 12:28, Oleg Kalnichevski <olegk@apache.org> wrote:
>
> ...
>
> > >> Issue is not present in HTTPCLient 3.1
> > >
> > > Philippe
> > >
> > > If HttpClient is used correctly, this code should only be executed only
> > > once. Why does JMeter create more than one instance of HttpClient?
> >
> > We currently create an instance for each instance of different proxy
> > settings and each protocol and each authority, because the client is
> > created with these settings.
> >
> > This is also done for each thread.
> >
> > IIRC, this was necessary originally. We have not rewritten the code
> > yet to use all the latest features.
> >
>
> I see. For the time what you can do is to use a custom SSL socket
> factory that lazily initializes SSL context when requested for the first
> time. This is exactly what HC 3.1 does. It will be somewhat slower given
> that one would need to mutex to synchronize access to the initialization
> code.
>
> Oleg
>
> > > Oleg
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
>
>
>


-- 
Cordialement.
Philippe Mouawad.

--047d7bdca2e8b30a4505275b4662--