You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2006/10/19 15:50:34 UTC
[jira] Created: (DIRMINA-292) Configurable dynamic assignment of
worker threads (acceptor, connector and I/O processor)
Configurable dynamic assignment of worker threads (acceptor, connector and I/O processor)
-----------------------------------------------------------------------------------------
Key: DIRMINA-292
URL: http://issues.apache.org/jira/browse/DIRMINA-292
Project: Directory MINA
Issue Type: New Feature
Components: Core
Reporter: Trustin Lee
Fix For: 1.1
As one IoService can manage only one service address, utilization of worker threads became an issue. For example, one connector can connect to only one remote address for simplicity while it produces one thread per instance. This is very inefficient way to utilize threads. The acceptor side doesn't have much difference. The problem becomes serious when a user implements a P2P application.
What we need to do is to provide a dynamic and configurable way to create and assign worker threads for all kinds of transports.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DIRMINA-292) Configurable dynamic assignment of
worker threads (acceptor, connector and I/O processor)
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trustin Lee updated DIRMINA-292:
--------------------------------
Fix Version/s: (was: 1.1)
2.0
> Configurable dynamic assignment of worker threads (acceptor, connector and I/O processor)
> -----------------------------------------------------------------------------------------
>
> Key: DIRMINA-292
> URL: https://issues.apache.org/jira/browse/DIRMINA-292
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Reporter: Trustin Lee
> Fix For: 2.0
>
>
> As one IoService can manage only one service address, utilization of worker threads became an issue. For example, one connector can connect to only one remote address for simplicity while it produces one thread per instance. This is very inefficient way to utilize threads. The acceptor side doesn't have much difference. The problem becomes serious when a user implements a P2P application.
> What we need to do is to provide a dynamic and configurable way to create and assign worker threads for all kinds of transports.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira