You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Michael Cetrulo <ma...@gmail.com> on 2012/01/04 23:49:51 UTC
is it bad to have lots of column families?
in a traditional database it's not a good a idea to have hundreds of tables
but is it also bad to have hundreds of column families in cassandra? thank
you.
Re: is it bad to have lots of column families?
Posted by Vitalii Tymchyshyn <ti...@gmail.com>.
Yes, as far as I know. Note, that it's not full index, but "sampling"
one. See index_interval configuration parameter and it's description.
As of bloom filters, it's not configurable now, yet there is a ticket
with a patch that should make it configurable.
05.01.12 22:45, Carlo Pires написав(ла):
> Does index for CFs must fit in node's memory?
>
> 2012/1/5 Віталій Тимчишин <tivv00@gmail.com <ma...@gmail.com>>
>
>
>
> 2012/1/5 Michael Cetrulo <mail2samus@gmail.com
> <ma...@gmail.com>>
>
> in a traditional database it's not a good a idea to have
> hundreds of tables but is it also bad to have hundreds of
> column families in cassandra? thank you.
>
>
> As far as I can see, this may raise memory requirements for you,
> since you need to have index/bloom filter for each column family
> in memory.
>
--
Best regards,
Vitalii Tymchyshyn
Re: is it bad to have lots of column families?
Posted by Carlo Pires <ca...@gmail.com>.
Does index for CFs must fit in node's memory?
2012/1/5 Віталій Тимчишин <ti...@gmail.com>
>
>
> 2012/1/5 Michael Cetrulo <ma...@gmail.com>
>
>> in a traditional database it's not a good a idea to have hundreds of
>> tables but is it also bad to have hundreds of column families in cassandra?
>> thank you.
>>
>
> As far as I can see, this may raise memory requirements for you, since you
> need to have index/bloom filter for each column family in memory.
>
> --
> Best regards,
> Vitalii Tymchyshyn
>
--
Carlo Pires
62 8209-1444 TIM
62 3251-1383
Skype: carlopires
Re: is it bad to have lots of column families?
Posted by Віталій Тимчишин <ti...@gmail.com>.
2012/1/5 Michael Cetrulo <ma...@gmail.com>
> in a traditional database it's not a good a idea to have hundreds of
> tables but is it also bad to have hundreds of column families in cassandra?
> thank you.
>
As far as I can see, this may raise memory requirements for you, since you
need to have index/bloom filter for each column family in memory.
--
Best regards,
Vitalii Tymchyshyn
Re: is it bad to have lots of column families?
Posted by Philippe <wa...@gmail.com>.
My 0.8 production cluster contains around 150 CFs spread across 5
keyspaces. Haven't found that to be an issue (yet?).
Some of them are huge (dozens of GB), some are tiny (some MB).
Cheers
2012/1/5 aaron morton <aa...@thelastpickle.com>
> Sort of. Depends.
>
> In Cassandra automatic memory management means the server can support more
> CF's and it has apparently been tested to 100's or 1000's of CF's. Having
> lots of CF's will impact performance by putting memory and IO under
> pressure though.
>
> If you have 10's you should not have to worry too much. Best thing is to
> test and post your findings.
>
> Hope that helps.
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 5/01/2012, at 11:49 AM, Michael Cetrulo wrote:
>
> in a traditional database it's not a good a idea to have hundreds of
> tables but is it also bad to have hundreds of column families in cassandra?
> thank you.
>
>
>
Re: is it bad to have lots of column families?
Posted by aaron morton <aa...@thelastpickle.com>.
Sort of. Depends.
In Cassandra automatic memory management means the server can support more CF's and it has apparently been tested to 100's or 1000's of CF's. Having lots of CF's will impact performance by putting memory and IO under pressure though.
If you have 10's you should not have to worry too much. Best thing is to test and post your findings.
Hope that helps.
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 5/01/2012, at 11:49 AM, Michael Cetrulo wrote:
> in a traditional database it's not a good a idea to have hundreds of tables but is it also bad to have hundreds of column families in cassandra? thank you.