[
https://issues.apache.org/jira/browse/CASSANDRA-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Norberg updated CASSANDRA-5422:
--------------------------------------
Attachment: ExecuteMessage Profiling - Hot Spots.png
ExecuteMessage Profiling - Call Tree.png
> 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
