cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3634) compare string vs. binary prepared statement parameters
Date Sat, 24 Dec 2011 07:56:33 GMT


Jonathan Ellis commented on CASSANDRA-3634:

Let's get Brandon to do some testing on our cluster with separate clients and servers.  If
strings are testing faster than binary then either

# something is wrong with the code, because parsing String -> ByteBuffer can't possibly
be faster than just using the ByteBuffer from Thrift (not to mention that Thrift's internal
creation of the String object has more overhead than marking a ByteBuffer slice of the frame)
# the difference is negligible compared to other factors and the test noise
# the difference is hidden by environmental factors, e.g., String runs just as fast as BB
but with X% more CPU used

Splitting out clients/servers will help determine if #3 is playing a role here.
> compare string vs. binary prepared statement parameters
> -------------------------------------------------------
>                 Key: CASSANDRA-3634
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>            Priority: Minor
>              Labels: cql
>             Fix For: 1.1
>         Attachments: stress-change-bind-parms-to-BB.patch, v1-0001-CASSANDRA-3634-generated-thrift-code.txt,
> Perform benchmarks to compare the performance of string and pre-serialized binary parameters
to prepared statements.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message