> But when modeling the application I understand so far that ColumnFamily is
> sort of "table with objects". In typical application there are lot of tables
> so why is the mindset set towards having more or less 10 ColumnFamilies?
> Even in this trivial example there are already 7 CFs
> http://www.
On 13.2.2011 11:40, Peter Schuller wrote:
Reading in the documentation (specially on the tuning section) is clear the
the number of Column Families affects the performance, in particular the
amount of memory assigned to the heap.
My question is: What's the hard limit on the number of CFs?
Does a
> Reading in the documentation (specially on the tuning section) is clear the
> the number of Column Families affects the performance, in particular the
> amount of memory assigned to the heap.
> My question is: What's the hard limit on the number of CFs?
> Does anybody implemented an application w
I asked a similar question (but didn't receive an answer). I'm trying to see
if a large number of CFs might be beneficial. One thing I can think about is
the size of extra storage needed for compaction -- obviously it will be
smaller in case of many smaller CFs.
--
View this message in context:
