You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Mohit Anchlia <mo...@gmail.com> on 2012/03/25 03:25:00 UTC
Performance overhead when using start and end columns
I have rows with around 2K-50K columns but when I do a query I only need to
fetch few columns between start and end columns. I was wondering what
performance overhead does it cause by using slice query with start and end
columns?
Looking at the code it looks like when you give start and end column it
goes in IndexSliceReader logic, but it's hard to tell how much overhead on
an average one would see? Or is it even worth worrying about?
Re: Performance overhead when using start and end columns
Posted by Data Craftsman <da...@gmail.com>.
Hi Aaron,
Thanks for the benchmark. The matrix is valuable.
Thanks,
Charlie (@mujiang) 一个 木匠
=======
Data Architect Developer
http://mujiang.blogspot.com
On Mon, Mar 26, 2012 at 10:53 AM, aaron morton <aa...@thelastpickle.com> wrote:
> See the test's in the article.
>
> The code I used for profiling is also available.
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 27/03/2012, at 6:21 AM, Mohit Anchlia wrote:
>
> Thanks but if I do have to specify start and end columns then how much
> overhead roughly would that translate to since reading metadata should be
> constant overall?
>
> On Mon, Mar 26, 2012 at 10:18 AM, aaron morton <aa...@thelastpickle.com>
> wrote:
>>
>> Some information on query plans
>> http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
>>
>> Tl;Dr; Select columns with no start, in the natural Comparator order.
>>
>> Cheers
>>
>>
>> -----------------
>> Aaron Morton
>> Freelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 25/03/2012, at 2:25 PM, Mohit Anchlia wrote:
>>
>> I have rows with around 2K-50K columns but when I do a query I only need
>> to fetch few columns between start and end columns. I was wondering what
>> performance overhead does it cause by using slice query with start and end
>> columns?
>>
>> Looking at the code it looks like when you give start and end column it
>> goes in IndexSliceReader logic, but it's hard to tell how much overhead on
>> an average one would see? Or is it even worth worrying about?
>>
>>
>
>
Re: Performance overhead when using start and end columns
Posted by "R. Verlangen" <ro...@us2.nl>.
@Aaron: Very interesting article! Mentioned it on my Dutch blog.
2012/3/26 Mohit Anchlia <mo...@gmail.com>
> Thanks!
>
>
> On Mon, Mar 26, 2012 at 10:53 AM, aaron morton <aa...@thelastpickle.com>wrote:
>
>> See the test's in the article.
>>
>> The code I used for profiling is also available.
>>
>> Cheers
>>
>> -----------------
>> Aaron Morton
>> Freelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 27/03/2012, at 6:21 AM, Mohit Anchlia wrote:
>>
>> Thanks but if I do have to specify start and end columns then how much
>> overhead roughly would that translate to since reading metadata should be
>> constant overall?
>>
>> On Mon, Mar 26, 2012 at 10:18 AM, aaron morton <aa...@thelastpickle.com>wrote:
>>
>>> Some information on query plans
>>> http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
>>>
>>> Tl;Dr; Select columns with no start, in the natural Comparator order.
>>>
>>> Cheers
>>>
>>>
>>> -----------------
>>> Aaron Morton
>>> Freelance Developer
>>> @aaronmorton
>>> http://www.thelastpickle.com
>>>
>>> On 25/03/2012, at 2:25 PM, Mohit Anchlia wrote:
>>>
>>> I have rows with around 2K-50K columns but when I do a query I only
>>> need to fetch few columns between start and end columns. I was wondering
>>> what performance overhead does it cause by using slice query with start and
>>> end columns?
>>>
>>> Looking at the code it looks like when you give start and end column it
>>> goes in IndexSliceReader logic, but it's hard to tell how much overhead on
>>> an average one would see? Or is it even worth worrying about?
>>>
>>>
>>>
>>
>>
>
--
With kind regards,
Robin Verlangen
www.robinverlangen.nl
Re: Performance overhead when using start and end columns
Posted by Mohit Anchlia <mo...@gmail.com>.
Thanks!
On Mon, Mar 26, 2012 at 10:53 AM, aaron morton <aa...@thelastpickle.com>wrote:
> See the test's in the article.
>
> The code I used for profiling is also available.
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 27/03/2012, at 6:21 AM, Mohit Anchlia wrote:
>
> Thanks but if I do have to specify start and end columns then how much
> overhead roughly would that translate to since reading metadata should be
> constant overall?
>
> On Mon, Mar 26, 2012 at 10:18 AM, aaron morton <aa...@thelastpickle.com>wrote:
>
>> Some information on query plans
>> http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
>>
>> Tl;Dr; Select columns with no start, in the natural Comparator order.
>>
>> Cheers
>>
>>
>> -----------------
>> Aaron Morton
>> Freelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 25/03/2012, at 2:25 PM, Mohit Anchlia wrote:
>>
>> I have rows with around 2K-50K columns but when I do a query I only
>> need to fetch few columns between start and end columns. I was wondering
>> what performance overhead does it cause by using slice query with start and
>> end columns?
>>
>> Looking at the code it looks like when you give start and end column it
>> goes in IndexSliceReader logic, but it's hard to tell how much overhead on
>> an average one would see? Or is it even worth worrying about?
>>
>>
>>
>
>
Re: Performance overhead when using start and end columns
Posted by aaron morton <aa...@thelastpickle.com>.
See the test's in the article.
The code I used for profiling is also available.
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 27/03/2012, at 6:21 AM, Mohit Anchlia wrote:
> Thanks but if I do have to specify start and end columns then how much overhead roughly would that translate to since reading metadata should be constant overall?
>
> On Mon, Mar 26, 2012 at 10:18 AM, aaron morton <aa...@thelastpickle.com> wrote:
> Some information on query plans
> http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
>
> Tl;Dr; Select columns with no start, in the natural Comparator order.
>
> Cheers
>
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 25/03/2012, at 2:25 PM, Mohit Anchlia wrote:
>
>> I have rows with around 2K-50K columns but when I do a query I only need to fetch few columns between start and end columns. I was wondering what performance overhead does it cause by using slice query with start and end columns?
>>
>> Looking at the code it looks like when you give start and end column it goes in IndexSliceReader logic, but it's hard to tell how much overhead on an average one would see? Or is it even worth worrying about?
>
>
Re: Performance overhead when using start and end columns
Posted by Mohit Anchlia <mo...@gmail.com>.
Thanks but if I do have to specify start and end columns then how much
overhead roughly would that translate to since reading metadata should be
constant overall?
On Mon, Mar 26, 2012 at 10:18 AM, aaron morton <aa...@thelastpickle.com>wrote:
> Some information on query plans
> http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
>
> Tl;Dr; Select columns with no start, in the natural Comparator order.
>
> Cheers
>
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 25/03/2012, at 2:25 PM, Mohit Anchlia wrote:
>
> I have rows with around 2K-50K columns but when I do a query I only need
> to fetch few columns between start and end columns. I was wondering what
> performance overhead does it cause by using slice query with start and end
> columns?
>
> Looking at the code it looks like when you give start and end column it
> goes in IndexSliceReader logic, but it's hard to tell how much overhead on
> an average one would see? Or is it even worth worrying about?
>
>
>
Re: Performance overhead when using start and end columns
Posted by aaron morton <aa...@thelastpickle.com>.
Some information on query plans
http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
Tl;Dr; Select columns with no start, in the natural Comparator order.
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 25/03/2012, at 2:25 PM, Mohit Anchlia wrote:
> I have rows with around 2K-50K columns but when I do a query I only need to fetch few columns between start and end columns. I was wondering what performance overhead does it cause by using slice query with start and end columns?
>
> Looking at the code it looks like when you give start and end column it goes in IndexSliceReader logic, but it's hard to tell how much overhead on an average one would see? Or is it even worth worrying about?