is good.
> >
> >
> > -----Original Message-
> > From: Artur Kronenberg [mailto:artur.kronenb...@openmarket.com]
> > Sent: Friday, October 18, 2013 1:03 PM
> > To: user@cassandra.apache.org
> > Subject: Re: Sorting keys for batch reads to minimize seeks
&g
;]
> Sent: Friday, October 18, 2013 1:03 PM
> To: user@cassandra.apache.org <mailto:user@cassandra.apache.org>
> Subject: Re: Sorting keys for batch reads to minimize seeks
>
> Hi,
>
> Thanks for your reply. Our latency currently is 23.618ms. However I
simply read that
Kronenberg [mailto:artur.kronenb...@openmarket.com]
> Sent: Friday, October 18, 2013 1:03 PM
> To: user@cassandra.apache.org
> Subject: Re: Sorting keys for batch reads to minimize seeks
>
> Hi,
>
> Thanks for your reply. Our latency currently is 23.618ms. However I
simply read t
orting keys for batch reads to minimize seeks
Hi,
Thanks for your reply. Our latency currently is 23.618ms. However I simply read
that off one node just now while it wasn't under a load test. I am going to be
able to get a better number after the next test run.
What is a good value for read
Hi,
Thanks for your reply. Our latency currently is 23.618ms. However I
simply read that off one node just now while it wasn't under a load
test. I am going to be able to get a better number after the next test run.
What is a good value for read latency?
On 18/10/13 08:31, Viktor Jevdokimov
> Sorting a random set of keys will not help.
False
> If you know that you set of keys are on a particular node, then sorting might
> help.
True
Two different answers to the same question.
> But I doubt that it is a sound practice, given that sets of keys can be moved
> - as nodes ar
The only thing you may win - avoid unnecessary network hops if:
- request sorted keys (by token) from appropriate replica with
ConsistencyLevel.ONE and "dynamic_snitch: false".
- nodes has the same load
- replica not doing GC, and GC pauses are much higher than internode
communication.
For multi
Unless I misunderstood your statement on sorting by row keys,
Cassandra partitions rows across nodes based on row keys. Sorting a random
set of keys will not help.
If you know that you set of keys are on a particular node , then sorting
might help. But I doubt that it is a sound practice, given th
