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 Wed, 11 Jan 2012 23:14:39 GMT


Jonathan Ellis commented on CASSANDRA-3634:

My reasoning is, there aren't a whole lot of places left to pick up an extra 10% performance...
 Two years ago, or one, maybe 10% isn't such a big deal since there's so much left to optimize.
 That's no longer the case; I don't think we should knowingly lock our next-gen interface
into a lower-performing design.  Once made, we're stuck with this decision, or at least with
a really, really high barrier to change it.

On the other hand, we have the downside of extra complexity for the driver authors.  While
this is a valid point, it's a finite one -- once a prepared statement api has been created
and debugged, binary vs strings isn't going to matter.  It's a one-time fee in exchange for
better performance forever.  Additionally, sample binary marshalling code already exists for
any language with a Thrift driver.  So we're really talking about a relatively small amount
of work to build a binary-based PS api, over a String one.
> 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
> 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