[ 
https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175733#comment-13175733
 ] 

Eric Evans commented on CASSANDRA-3634:
---------------------------------------

bq. Let's get Brandon to do some testing on our cluster with separate clients 
and servers.

I've started another run with one client, one server, but having another set of 
results would be great, thanks.

bq. If strings are testing faster than binary then either

I don't think strings are faster.  The differences between String and BB for 
the insert-with-index, counter-increment, and read tests are very small, (i.e. 
we're looking at #2 here).

I believe the reason the insert-with-index and counter increment tests would 
fail to show a significant difference is because those operations push the 
contention needle in a different direction.  This is consistent with the fact 
that vanilla CQL fares so much better against thrift on these tests.  Also, the 
counter increment test only has one bind var (the key), so I would expect the 
difference to be quite small.

Like the counter increment test, the read test also only has one bind var 
(again the key), so I would likewise expect any difference to be lost in the 
noise.

The insert test above _does_ indicate some difference, BB beats out Strings by 
4% (5 columns equates to 11 bind vars here).  I don't have the results in front 
of me, but I ran a new insert test last night and I believe this increases to 
about 10% at 10x the number of columns.

The choice of initial tests here were based on what I had run earlier (to make 
the obligatory before/after comparison).  Those are still relevant I think, but 
to get a better idea of BB vs String, we need some results for insert tests 
with higher column counts (w/ client and server split to rule out #3 above).
                
> compare string vs. binary prepared statement parameters
> -------------------------------------------------------
>
>                 Key: CASSANDRA-3634
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3634
>             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, 
> v1-0002-change-bind-parms-from-string-to-bytes.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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to