Thankyou for making these issues clear. Currently, in my datamodel, I have
the current second( seconds-from-epoch) as the row key and micro second
with the client number as the column key.
Hence, all the packets received during a particular second
on all the clients are stored in t
> Each client is writing to a separate keyspace simultaneously. Hence, is there
> a lot of switching of keyspaces?
>
>
I would think not. If the client app is using one keyspace per connection there
should be no reason for the driver to change keyspaces.
> But, I observed that when using a
Hello,
Thanks for the reply. Currently, each client is writing about 470 packets
per second where each packet is 1500 bytes. I have four clients writing
simultaneously to the cluster. Each client is writing to a separate
keyspace simultaneously. Hence, is there a lot of switching of keyspaces?
> On the homepage of libQtCassandra, its mentioned that switching between
> keyspaces is costly when storing into Cassandra thereby affecting the write
> throughput. Is this necessarily true for other libraries like pycassa and
> hector as well?
>
>
When using the thrift connection the keyspac
