cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-8457) nio MessagingService
Date Fri, 12 Dec 2014 15:19:15 GMT

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

Ryan McGuire edited comment on CASSANDRA-8457 at 12/12/14 3:19 PM:
-------------------------------------------------------------------

[~benedict] modifying cstar_perf to run multiple instances per node is a larger task, and
I'm wondering how useful that will be (seems like a lot of resource contention / non-real-world
variables.) Assuming we had the alternative of 100% automated EC2 cluster bootstrapping/teardown,
how often would we want to run these larger tests for it to be worth it? 


was (Author: enigmacurry):
@Benedict modifying cstar_perf to run multiple instances per node is a larger task, and I'm
wondering how useful that will be (seems like a lot of resource contention / non-real-world
variables.) Assuming we had the alternative of 100% automated EC2 cluster bootstrapping/teardown,
how often would we want to run these larger tests for it to be worth it? 

> 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)

Mime
View raw message