Thanks Jonathan, actually I'm wondering how CQL is implemented underlying,
a different RPC mechanism? Why it is faster than thrift? I know I'm wrong,
but now I just regard CQL as a query language. Could you please help
explain to me? I still feel puzzled after reading some docs about CQL. I
create
cassandra-stress is a great tool to check whether the sizing of your cluster in
combination of your data model will fit your production needs. I.e. without the
application :) Removing the application removes any possible bugs from the load
test. Sure, it’s a necessary step to do it with your
I agree with Robert. If you're trying to test Cassandra, test Cassandra
using stress. Set a reasonable benchmark, and then you'll be able to aim
for that with your client code. Otherwise you're likely to be asking a lot
of the wrong questions make incorrect assumptions.
On Mon Dec 08 2014 at
Thanks Robert. So the native protocol is an asynchronous protocol? And is
native protocol specially created for Cassandra CQL? I haven't heard about
this protocol before.
I have tried using the stress test tool. But it seems that this tool should
run on the same node as one of the Cassandra
So the native protocol is an asynchronous protocol?
Yes.
I have tried using the stress test tool. But it seems that this tool should
run on the same node as one of the Cassandra node(or at least on a node
having Cassandra installed)? One I try to run this tool on a separate client
What's a ring cache?
FYI if you're using the DataStax CQL drivers they will automatically route
requests to the correct node.
On Sun Dec 07 2014 at 12:59:36 AM kong kongjiali...@gmail.com wrote:
Hi,
I'm doing stress test on Cassandra. And I learn that using ring cache can
improve the
I find under the src/client folder of Cassandra 2.1.0 source code, there is
a *RingCache.java* file. It uses a thrift client calling the*
describe_ring()* API to get the token range of each Cassandra node. It is
used on the client side. The client can use it combined with the
partitioner to get
I would really not recommend using thrift for anything at this point,
including your load tests. Take a look at CQL, all development is going
there and has in 2.1 seen a massive performance boost over 2.0.
You may want to try the Cassandra stress tool included in 2.1, it can
stress a table
