On Fri, Dec 10, 2010 at 2:45 PM, Peter Schuller 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 "
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