+1 to everything Eric said.
The penalty of not using token aware routing increases as you add nodes,
load, and network overhead. This is kind of like batch statements. People
use them in dev, with 1 node, and think they're great to help with
performance. But when you put them in production... n
That's not a particularly good setup for load testing, I would try hard not
to draw any conclusions from it. Most likely your biggest bottleneck is
I/O in your VM's, and any savings from using prepared statements dwarf in
comparison to the price of virtualization. Point 2's effects are also
minim
Thanks Eric. I didn't know the point about the token aware routing.
But with points 2 and 3 I didn't notice much improvement with prepared
statement. I have 2 cassandra nodes running in virtual boxes in the same
machine and test client running in the same machine.
Thanks
Ajay
Prepared statements
Prepared statements can take advantage of token aware routing which IIRC
non-prepared statements cannot in the DS Java Driver, so as your cluster
grows you reduce the overhead of statement coordination (assuming you use
token aware routing). There should also be less data to transfer for
shipping
Hi All,
I tried both insert and select query (using QueryBuilder) in Regular
statement and PreparedStatement in a multithreaded code to do the query say
10k to 50k times. But I don't see any visible improvement using the
PreparedStatement. What could be the reason?
Note : I am using the same Sess
