From 0ee0bc6d7be7f127b3a4494c7b66185a184d66df Mon Sep 17 00:00:00 2001 From: Jonathan Ellis Date: Mon, 14 Mar 2011 22:19:10 +0000 Subject: [PATCH] r/m disk_access_mode from sample yaml git-svn-id: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@1081586 13f79535-47bb-0310-9956-ffa450edef68 --- conf/cassandra.yaml | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 95884f1675..2e518deffa 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -124,16 +124,6 @@ reduce_cache_capacity_to: 0.6 seeds: - 127.0.0.1 -# Access mode. mmapped i/o is substantially faster, but only practical on -# a 64bit machine (which notably does not include EC2 "small" instances) -# or relatively small datasets. "auto", the safe choice, will enable -# mmapping on a 64bit JVM. Other values are "mmap", "mmap_index_only" -# (which may allow you to get part of the benefits of mmap on a 32bit -# machine by mmapping only index files) and "standard". -# (The buffer size settings that follow only apply to standard, -# non-mmapped i/o.) -disk_access_mode: auto - # For workloads with more data than can fit in memory, Cassandra's # bottleneck will be reads that need to fetch data from # disk. "concurrent_reads" should be set to (16 * number_of_drives) in