Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 4 May 2016 21:07:12 +0000 (UTC)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12843761.1436418814000.112880.1462396032833@Atlassian.JIRA>
In-Reply-To: <JIRA.12843761.1436418814000@Atlassian.JIRA>
References: <JIRA.12843761.1436418814000@Atlassian.JIRA> <JIRA.12843761.1436418814978@arcas>
Subject: [jira] [Updated] (CASSANDRA-9766) Faster Streaming
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 May 2016 21:07:14 -0000


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

T Jake Luciani updated CASSANDRA-9766:
--------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.x)
                   3.8
           Status: Resolved  (was: Patch Available)

committed {{1e92ce43a5a730f81d3f6cfd72e7f4b126db788a}}

> Faster Streaming
> ----------------
>
>                 Key: CASSANDRA-9766
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9766
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Streaming and Messaging
>         Environment: Cassandra 2.1.2. more details in the pdf attached 
>            Reporter: Alexei K
>            Assignee: T Jake Luciani
>              Labels: performance
>             Fix For: 3.8
>
>         Attachments: problem.pdf
>
>
> I have a cluster in Amazon cloud , its described in detail in the attachment. What I've noticed is that we during bootstrap we never go above 12MB/sec transmission speeds and also those speeds flat line almost like we're hitting some sort of a limit ( this remains true for other tests that I've ran) however during the repair we see much higher,variable sending rates. I've provided network charts in the attachment as well . Is there an explanation for this? Is something wrong with my configuration, or is it a possible bug?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)