You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by 박용욱 <co...@gmail.com> on 2011/04/13 15:28:41 UTC

choose which Hector's serializer for Cassandra performance?

I have questions below.

1. In cassandra server, row key, column name and column value are saved in
byte[], aren't they?

2. If I call hector's mutator.addInsertion(rowKey, cfName, HColumn<String,
Integer>), does the transformation from String/Integer to byte[] occur at
client? or server?

3. If 2 occurs at server, then which Type should I use with HColumn<Type,
Type> to get the most performance of cassandra? client performance is out of
concerns.


4. with RF 3 and random partitioner, does read iterations(paging) with range
query work well? I mean whether row-keys order changes over iterations or
not? (CL is QUORUM)

Sencerely.
Colin.

Re: choose which Hector's serializer for Cassandra performance?

Posted by aaron morton <aa...@thelastpickle.com>.

1. Order for RP is, well, random'ish for some large value of ish see http://wiki.apache.org/cassandra/FAQ#range_rp

2. Not really. 

Aaron

On 14 Apr 2011, at 14:45, 박용욱 wrote:

> Thanks very much Aaron!
> 
> 4. Not sure how Hector handles it, try https://github.com/zznate/cassandra-tutorial or https://github.com/zznate/hector-examples
> 
> 
> Let me ask question 4 again. :)
> 
> 
> 1. RandomPartitioner and OrderPreservingPartitioner response same result for get_range_slices API.
> 
>           Is the only difference is efficiency?
> 2.  Don't RF & CL influence get_range_slices API, do they?
> 
> 
> 
> 
> Best Reguards.
> Colin.

Re: choose which Hector's serializer for Cassandra performance?

Posted by 박용욱 <co...@gmail.com>.

Thanks very much Aaron!

4. Not sure how Hector handles it, try
https://github.com/zznate/cassandra-tutorial or
https://github.com/zznate/hector-examples


<https://github.com/zznate/hector-examples>Let me ask question 4 again. :)

1. RandomPartitioner and OrderPreservingPartitioner response same result
for get_range_slices API.
          Is the only difference is efficiency?
2.  Don't RF & CL influence get_range_slices API, do they?

Best Reguards.
Colin.

Re: choose which Hector's serializer for Cassandra performance?

Posted by Aaron Morton <aa...@thelastpickle.com>.

1. Yes
2. Client
3. NA
4. Not sure how Hector handles it, try https://github.com/zznate/cassandra-tutorial or https://github.com/zznate/hector-examples

Aaron

On 14/04/2011, at 1:28 AM, 박용욱 <co...@gmail.com> wrote:

> I have questions below.
> 
> 1. In cassandra server, row key, column name and column value are saved in byte[], aren't they?
> 
> 2. If I call hector's mutator.addInsertion(rowKey, cfName, HColumn<String, Integer>), does the transformation from String/Integer to byte[] occur at client? or server?
> 
> 3. If 2 occurs at server, then which Type should I use with HColumn<Type, Type> to get the most performance of cassandra? client performance is out of concerns.
> 
> 
> 4. with RF 3 and random partitioner, does read iterations(paging) with range query work well? I mean whether row-keys order changes over iterations or not? (CL is QUORUM)
> 
> Sencerely.
> Colin.