[
https://issues.apache.org/jira/browse/SSHD-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294356#comment-17294356
]
Susmit Sarkar commented on SSHD-1135:
-------------------------------------
I was finding the analogy of NIO2 thread workers with executor thread pool
> Configurable sshd transfer threads
> ----------------------------------
>
> Key: SSHD-1135
> URL: https://issues.apache.org/jira/browse/SSHD-1135
> Project: MINA SSHD
> Issue Type: Question
> Reporter: Susmit Sarkar
> Priority: Critical
>
> Set the number of transfer threads. Once a socket has either been accepted or
> connected, the socket is registered with a transfer thread. This thread
> asynchronously performs all the IO for the socket. If all the permanent
> threads become fully loaded then additional threads will be created to handle
> additional connections and shutdown once they have no sockets to service.
>
> Is there any performance tuning parameter that we can use to leverage our
> above use case?
> I know if we use socketImplementation default (NIO2) there is a configuration
> value called {{nio-workers. Will it serve our purpose?}}
> And if so what are the upper boundary limits for the value nio-worker
>
> (Property.integer("nio-workers", Runtime.getRuntime().availableProcessors() +
> X)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
