cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3634) compare string vs. binary prepared statement parameters
Date Wed, 11 Jan 2012 20:45:39 GMT


Eric Evans commented on CASSANDRA-3634:

It's more compelling to me when compared in the context of the existing RPC performance. 5%
is gain okay (PS vs RPC), but 16% (BB vs RPC) is a fairly substantial improvement.

I was a little worried about the variance (even though the worst cases are pretty close) but
I ran some tests with the commit log disable and the deviation is on par with the rest, I
think it's just fast enough to push it that hard.

That's interesting.  I got so wrapped up in the {{ByteBuffer}} vs. {{String}} comparison that
I lost track of the fact that your results put CQL w/ prepared statements ahead of RPC _across
the board_ (which is the most important take-away from this I hope!).  That would mean that
you're willing to trade that node-side abstraction for performance that is _already above-and-beyond_
RPC.  I think I completely overestimated how compelling the simplicity/abstraction vs performance
trade-off argument would be to folks.
> 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