cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5422) Binary protocol sanity check
Date Mon, 20 May 2013 02:11:16 GMT

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

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

That said, the appropriate place for a Spotify copyright notice would be the header file:

{quote}
If [a] source file is submitted with a copyright notice included in it, the copyright owner
(or owner's agent) must either:
# remove such notices, or
# move them to the NOTICE file associated with each applicable project release, or
# provide written permission for the ASF to make such removal or relocation of the notices.
{quote}

http://www.apache.org/legal/src-headers.html
                
> 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

Mime
View raw message