You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2011/01/03 19:08:45 UTC

[jira] Updated: (THRIFT-965) Use a queue instead of a set to record interest changes in NonblockingServer

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

Bryan Duxbury updated THRIFT-965:
---------------------------------

    Fix Version/s:     (was: 0.6)
                   0.7

> Use a queue instead of a set to record interest changes in NonblockingServer
> ----------------------------------------------------------------------------
>
>                 Key: THRIFT-965
>                 URL: https://issues.apache.org/jira/browse/THRIFT-965
>             Project: Thrift
>          Issue Type: Improvement
>    Affects Versions: 0.2, 0.3, 0.4, 0.5
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>             Fix For: 0.7
>
>
> Right now we use a HashSet to record interest changes. This requires us to synchronize on access to it which seems like an unnecessary contention bottleneck. Instead, if we used a queue, we could do standard producer/consumer and use more granular locks (if any).

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