[ https://issues.apache.org/jira/browse/THRIFT-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046279#comment-13046279 ]
Bryan Duxbury commented on THRIFT-1167: --------------------------------------- OK, that helps a lot. Here's one question I've been trying to solve. In this architecture, does a given socket get bound to a particular select thread for the lifetime of the connection, or do the sockets move around between selectors opportunistically? > Java nonblocking server with more than one thread for select and handling IO > ---------------------------------------------------------------------------- > > Key: THRIFT-1167 > URL: https://issues.apache.org/jira/browse/THRIFT-1167 > Project: Thrift > Issue Type: New Feature > Components: Java - Library > Reporter: Steve Jiang > Assignee: Bryan Duxbury > Attachments: threadedselectorthrift3.diff > > > I've used the HsHa server model to write a server that uses a thread for > accept and a separate, configurable number of Selector threads to handle IO. > I'd like to contribute this back to Thrift. > For apps that are RPC-heavy and require little computation from the executor > pool running on multi-core architectures, this server allows gets throughput > as IO is not limited by one CPU. > Please take a look at the attached patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira