Re: RE: Consequences of having many columns

2010-07-13 Thread Aaron Morton
ache.org Subject: Re: Consequences of having many columns   Currently there is a limitation that each row must fit in memory (with some not insignificant overhead), thus having lots of columns per row can trigger out-of-memory errors. This limitation should be removed in a future release. 

RE: Consequences of having many columns

2010-07-13 Thread Kochheiser,Todd W - TOK-DITT-1
: Tuesday, July 13, 2010 8:41 AM To: user@cassandra.apache.org Subject: Re: Consequences of having many columns Currently there is a limitation that each row must fit in memory (with some not insignificant overhead), thus having lots of columns per row can trigger out-of-memory errors. This

Re: Consequences of having many columns

2010-07-13 Thread Mason Hale
Currently there is a limitation that each row must fit in memory (with some not insignificant overhead), thus having lots of columns per row can trigger out-of-memory errors. This limitation should be removed in a future release. Please see: - http://wiki.apache.org/cassandra/CassandraLimitation

Consequences of having many columns

2010-07-13 Thread Kochheiser,Todd W - TOK-DITT-1
I recently ran across a blog posting with a comment from a Cassandra committer that indicated a performance penalty when having a large number of columns per row/key. Unfortunately I didn't bookmark the blog posting and now I can't find it. Regardless, since our current plan and design is to h