[jira] [Updated] (CASSANDRA-5422) Binary protocol sanity check

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis updated CASSANDRA-5422:
--------------------------------------

    Attachment: 5422-test.txt

Patch to disable MS.execute (and batch_mutate) attached.

To run the binary protocol stress test,

{{mvn install -Dmaven.test.skip=true}} from java-driver root (https://github.com/datastax/java-driver)

then {{mvn assembly:single from driver-example/stress}}

finally, {{java -jar target/cassandra-driver-examples-stress-1.0.0-beta2-APSHOT-jar-with-dependencies.jar insert_prepared --value-size 4}}
                
> 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: Marcus Eriksson
>         Attachments: 5422-test.txt
>
>
> 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