Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 12 Jul 2016 06:30:11 +0000 (UTC)
From: "Jason Brown (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12760861.1418247068000.88461.1468305011349@Atlassian.JIRA>
In-Reply-To: <JIRA.12760861.1418247068000@Atlassian.JIRA>
References: <JIRA.12760861.1418247068000@Atlassian.JIRA> <JIRA.12760861.1418247068598@arcas>
Subject: [jira] [Commented] (CASSANDRA-8457) nio MessagingService
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 12 Jul 2016 06:30:13 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372251#comment-15372251 ] 

Jason Brown commented on CASSANDRA-8457:
----------------------------------------

I've pushed a new commit to the same branch after addressing the comments from [~norman] and Scott Mitchell - thanks guys for the feedback!. Tests running now.

> nio MessagingService
> --------------------
>
>                 Key: CASSANDRA-8457
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8457
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jonathan Ellis
>            Assignee: Jason Brown
>            Priority: Minor
>              Labels: netty, performance
>             Fix For: 4.x
>
>
> 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)