[
https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266422#comment-14266422
]
Ariel Weisberg commented on CASSANDRA-8457:
-------------------------------------------
https://forums.aws.amazon.com/thread.jspa?messageID=459260
This looks like a Xen/EC2 issue. I'll bet bare metal never has this issue
because it has multiple interrupt vectors for NICs. The only work around is
using multiple elastic network interfaces and doing something to make that
practical for intra-cluster communication.
> nio MessagingService
> --------------------
>
> Key: CASSANDRA-8457
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8457
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Ariel Weisberg
> Labels: performance
> Fix For: 3.0
>
>
> Thread-per-peer (actually two each incoming and outbound) is a big
> contributor to context switching, especially for larger clusters. Let's look
> at switching to nio, possibly via Netty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
