Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 20 May 2013 02:15:16 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12640517.1364997405516.345150.1369016116378@arcas>
In-Reply-To: <JIRA.12640517.1364997405516@arcas>
References: <JIRA.12640517.1364997405516@arcas>
Subject: [jira] [Commented] (CASSANDRA-5422) Binary protocol sanity check
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-5422:
-------------------------------------------

The rest of that page is interesting reading as well; basically, you retain copyright for your code whether or not it's actually explicitly specified, precisely since no copyright assignment is involved.  So while it's okay to add an entry to NOTICES, it's not actually useful for anything.

Very long thread about this at http://thread.gmane.org/gmane.comp.apache.legal.discuss/95
                
> Binary protocol sanity check
> ----------------------------
>
>                 Key: CASSANDRA-5422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5422
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: Daniel Norberg
>         Attachments: 5422-test.txt, ExecuteMessage Profiling - Call Tree.png, ExecuteMessage Profiling - Hot Spots.png
>
>
> With MutationStatement.execute turned into a no-op, I only get about 33k insert_prepared ops/s on my laptop.  That is: this is an upper bound for our performance if Cassandra were infinitely fast, limited by netty handling the protocol + connections.
> This is up from about 13k/s with MS.execute running normally.
> ~40% overhead from netty seems awfully high to me, especially for insert_prepared where the return value is tiny.  (I also used 4-byte column values to minimize that part as well.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira