On Tue, May 22, 2012 at 4:56 AM, samal <samalgo...@gmail.com> wrote: > Not ideally, now cass has global memtable tuning. Each cf correspond to > memory in ram. Year wise cf means it will be in read only state for next > year, memtable will still consume ram.
An empty memtable seems unlikely to consume a meaningful amount of RAM. I'm sure by reading the code I could estimate how little memory is involved, but I'd be surprised if it is over a few megabytes. This is independent from the other overhead associated with a CF being defined, of course. =Rob -- =Robert Coli AIM>ALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb
