gt; patterns, and your specific load. And it also depends on your own personal
> tolerance for degradation of latency and throughput - some people might find
> a given set of performance metrics acceptable while other might not.
>
> -- Jack Krupansky
>
> On Tue, Mar 1, 2
perations. Repairs were terribly slow, boot of C*
> slowed down and in general tracking table metrics becomes bit more work. Why
> do you need this high number of tables?
>
> Tommaso
>
> On Tue, Mar 1, 2016 at 9:16 AM, Fernando Jimenez
> mailto:fernando.jime...@wealth-port.co
gt; categories of table, or separate clusters for each few hundred of tables.
>
>
> -- Jack Krupansky
>
> On Mon, Feb 29, 2016 at 12:30 PM, Fernando Jimenez
> mailto:fernando.jime...@wealth-port.com>>
> wrote:
> Hi all
>
> I have a use case for Cassandra that wou
Hi all
I have a use case for Cassandra that would require creating a large number of
column families. I have found references to early versions of Cassandra where
each column family would require a fixed amount of memory on all nodes,
effectively imposing an upper limit on the total number of C
