camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomasz Kopczynski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10240) CamelHttpClient default pool size does not work on system with large number of cpus
Date Sat, 03 Sep 2016 09:17:20 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-10240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15460756#comment-15460756
] 

Tomasz Kopczynski commented on CAMEL-10240:
-------------------------------------------

I can work on this one. 
Just one question: do you also want to introduce a new parameter in the JettyHttpComponent
for the number of selectors?

> CamelHttpClient default pool size does not work on system with large number of cpus
> -----------------------------------------------------------------------------------
>
>                 Key: CAMEL-10240
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10240
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jetty
>    Affects Versions: 2.17.2
>            Reporter: Zoltan Farkas
>
> In CamelHttpClient a default threadpool is being created with a hardcoded size of 16:
> {code}
>     @Override
>     protected void doStart() throws Exception {
>         if (!hasThreadPool()) {
>             // if there is no thread pool then create a default thread pool using daemon
threads
>             QueuedThreadPool qtp = new QueuedThreadPool();
>             // 16 max threads is the default in the http client
>             qtp.setMaxThreads(16);
>             qtp.setDaemon(true);
>             // let the thread names indicate they are from the client
>             qtp.setName("CamelJettyClient(" + ObjectHelper.getIdentityHashCode(this)
+ ")");
>             setThreadPoolOrExecutor(qtp);
>         }
>         super.doStart();
>     }
> {code}
> this configuration does not work because number of selectors is calculated relative to
the number of CPUs in HttpClientTransportOverHTTP:
> {code}
>    public HttpClientTransportOverHTTP()
>     {
>         this(Math.max(1, Runtime.getRuntime().availableProcessors() / 2));
>     }
> {code}
> As a result by default camel simply hangs on these systems...
> It would be nice if CamelHttpClient would have a constructor that set the HttpClientTransport
or at least the number of selectors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message