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 2007/11/08 06:27:50 UTC

[jira] Updated: (DIRMINA-292) Shared I/O processors.

     [ https://issues.apache.org/jira/browse/DIRMINA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee updated DIRMINA-292:
--------------------------------

    Description: Currently, I/O processor threads belong to its parent IoService, which means that I/O processors cannot be shared among different services.  This becomes a serious issue when more than one service is deployed into the same JVM.  Therefore, we need a way to share the I/O processors among the services with the same transport type.  (was: 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.)
       Assignee: Trustin Lee
        Summary: Shared I/O processors.  (was: Configurable dynamic assignment of worker threads (acceptor, connector and I/O processor))

Updated issue description; I think it is too difficult to provide sharing for acceptor and connector threads other than I/O processors.  So I just narrowed down the scope of this issue.  Moreover, what's most critical part if sharing I/O processors.  The acceptor and connector threads are not that busy to cause contention IMHO, and it will be no problem at all once DIRMINA-341 is resolved.

> Shared I/O processors.
> ----------------------
>
>                 Key: DIRMINA-292
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-292
>             Project: MINA
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Trustin Lee
>            Assignee: Trustin Lee
>             Fix For: 2.0.0-M1
>
>
> Currently, I/O processor threads belong to its parent IoService, which means that I/O processors cannot be shared among different services.  This becomes a serious issue when more than one service is deployed into the same JVM.  Therefore, we need a way to share the I/O processors among the services with the same transport type.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.