fic, and at this point they’re
>>> old versions (and performance varies version to version).
>>>
>>> - Jeff
>>>
>>> From: on behalf of Kevin Burton
>>> Reply-To: "user@cassandra.apache.org"
>>> Date: Sunday, August 23, 2015 at
@cassandra.apache.org"
>> Date: Sunday, August 23, 2015 at 2:58 PM
>> To: "user@cassandra.apache.org"
>> Subject: Re: Practical limitations of too many columns/cells ?
>>
>> Ah.. yes. Great benchmarks. If I’m interpreting them correctly it was
>> ~15x
Sunday, August 23, 2015 at 2:58 PM
> To: "user@cassandra.apache.org"
> Subject: Re: Practical limitations of too many columns/cells ?
>
> Ah.. yes. Great benchmarks. If I’m interpreting them correctly it was
> ~15x slower for 22 columns vs 2 columns?
>
> Guess we have to refactor again
g"
Subject: Re: Practical limitations of too many columns/cells ?
Ah.. yes. Great benchmarks. If I’m interpreting them correctly it was ~15x
slower for 22 columns vs 2 columns?
Guess we have to refactor again :-P
Not the end of the world of course.
On Sun, Aug 23, 2015 at 1:53 PM, Jeff
ile=nodes Averages from the middle 80% of
> values:interval_op_rate : 23489
>
> From: on behalf of Kevin Burton
> Reply-To: "user@cassandra.apache.org"
> Date: Sunday, August 23, 2015 at 1:02 PM
> To: "user@cassandra.apache.org"
> Subject: Practical limitation
middle 80% of values:
interval_op_rate : 23489
From: on behalf of Kevin Burton
Reply-To: "user@cassandra.apache.org"
Date: Sunday, August 23, 2015 at 1:02 PM
To: "user@cassandra.apache.org"
Subject: Practical limitations of too many columns/cells ?
Is there any ad
Is there any advantage to using say 40 columns per row vs using 2 columns
(one for the pk and the other for data) and then shoving the data into a
BLOB as a JSON object?
To date, we’ve been just adding new columns. I profiled Cassandra and
about 50% of the CPU time is spent on CPU doing compactio
