Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 092E7DB51 for ; Fri, 9 Nov 2012 17:42:22 +0000 (UTC) Received: (qmail 49941 invoked by uid 500); 9 Nov 2012 17:42:21 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 49892 invoked by uid 500); 9 Nov 2012 17:42:21 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 49884 invoked by uid 99); 9 Nov 2012 17:42:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 17:42:21 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [217.150.250.48] (HELO kalnich.nine.ch) (217.150.250.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 17:42:13 +0000 Received: from [192.168.1.147] (77-57-197-206.dclient.hispeed.ch [77.57.197.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by kalnich.nine.ch (Postfix) with ESMTPSA id ED659B801D4 for ; Fri, 9 Nov 2012 18:41:52 +0100 (CET) Message-ID: <1352482911.9629.21.camel@ubuntu> Subject: Re: Question about IOReactorConfig.soTimeout and IOReactorConfig.ioThreadCount From: Oleg Kalnichevski To: HttpClient User Discussion Date: Fri, 09 Nov 2012 18:41:51 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.0-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Fri, 2012-11-09 at 11:59 -0500, Sachin Nikumbh wrote: > Hi, > > I am evaluating HTTP Async client and have following questions. > > How's IOReactorConfig.soTimeout different > from CoreConnectionPNames.SO_TIMEOUT? I am looking into the code but it's > not very obvious to me yet. IOReactorConfig applies to the lower level components (such as I/O session components) whereas CoreConnectionPNames apply to the protocol (HTTP level) components. CoreConnectionPNames and everything HttpParams related will be deprecated in the next series of releases (4.3), which, hopefully, should make HC configuration API more obvious and easier to use. > Also, what parameter should be taken into > account while setting value of IOReactorConfig.ioThreadCount? I see that > it's being defaulted to number of processors. But if my client application > is going to generate hundreds of simultaneous requests, should I be > changing this parameter? > No, you should not. You do not want to have any CPU cores underutilized. At the same time there is no point having more I/O selectors that the CPU cores capable of running them. > In general, while using HTTP async client in high load environment, what > are the parameters that one needs to be aware of? > As usual, one needs to be careful with the connection pool settings. You probably do not want too many connections just sitting idle in the pool. At the same time you do not execution requests to pile up blocked by a limited number of available connections. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org