mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chuanwen chen (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DIRMINA-668) Modify the way we use IoProcessors
Date Fri, 04 Dec 2009 08:45:21 GMT

    [ https://issues.apache.org/jira/browse/DIRMINA-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785820#action_12785820
] 

chuanwen chen edited comment on DIRMINA-668 at 12/4/09 8:43 AM:
----------------------------------------------------------------

Not sure where requests will be blocked, or will you explain "cost a lot"?

      was (Author: cfsego):
    Not sure where requests will be blocked, or will you explain "cost lots"?
  
> Modify the way we use IoProcessors
> ----------------------------------
>
>                 Key: DIRMINA-668
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-668
>             Project: MINA
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-M4
>            Reporter: Emmanuel Lecharny
>             Fix For: 3.0.0-M1
>
>
> In the current code base, when accepting new connections, we pick a processor and register
the news connection within the internal selector. In other words, we have as many selectors
as we have IoProcessors.
> This is a potential problem if some request cost a lot to be executed, as every requests
waiting on this IoProcessor will be blocked.
> It would be way better to use a single selector which dispatches requests to an Executor,
as we will always have available threads ready to process the requests (unless the pool is
saturated, but then we have a bigger issue ...)

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


Mime
View raw message