cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Norberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5422) Native protocol sanity check
Date Sat, 01 Jun 2013 14:35:21 GMT


Daniel Norberg commented on CASSANDRA-5422:

I've gotten confirmation that my ICLA has been received by the ASF. Waiting for confirmation
that our Corporate CLA has also been successfully submitted.

My changes to the message serialization can be merged at will as they should be covered by
the ICLA.

The changes I made to the driver and stress application I have donated to the driver project
so you can use them as you wish.

I believe the write batcher could be incorporated in org.apache.cassandra.transport and then
used both in the driver and server without any legal difficulties.
> Native protocol sanity check
> ----------------------------
>                 Key: CASSANDRA-5422
>                 URL:
>             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:

View raw message