[
https://issues.apache.org/jira/browse/HTTPCORE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538438#comment-16538438
]
ASF GitHub Bot commented on HTTPCORE-532:
-----------------------------------------
Github user ok2c commented on the issue:
https://github.com/apache/httpcomponents-core/pull/68
@xiaohu-zhang Why? The I/O reactor distributes sessions across all
available workers equally. If you have n worker threads, all of them will get
started after n connections.
> IOReactor thread should be lazy started
> ---------------------------------------
>
> Key: HTTPCORE-532
> URL: https://issues.apache.org/jira/browse/HTTPCORE-532
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Reporter: silver9886
> Priority: Major
>
> SingleCoreIOReactor can be lazy started when it used. do not need to start
> all threads before
> any http request.
> resolve method is create new ioreactor thread every time there has new
> request util thread number limit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
