On Fri, Dec 10, 2010 at 2:45 PM, Peter Schuller <peter.schul...@infidyne.com > wrote:
> I was looking closer at sliced_buffer_size_in_kb and > column_index_size_in_kb and reached the conclusion that for the > purpose of I/O, these are irrelevant when using mmap:ed I/O mode > (which makes sense, since there is no way to use a "buffer size" when > all you're doing is touching memory). The only effect is that > column_index_size_in_kb still affects the size at which indexing > triggers, which is as advertised. > > Firstly, can anyone confirm/deny my interpretation? > That's correct. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
