cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbel...@apache.org
Subject svn commit: r1081586 - /cassandra/branches/cassandra-0.7/conf/cassandra.yaml
Date Mon, 14 Mar 2011 22:19:10 GMT
Author: jbellis
Date: Mon Mar 14 22:19:10 2011
New Revision: 1081586

URL: http://svn.apache.org/viewvc?rev=1081586&view=rev
Log:
r/m disk_access_mode from sample yaml

Modified:
    cassandra/branches/cassandra-0.7/conf/cassandra.yaml

Modified: cassandra/branches/cassandra-0.7/conf/cassandra.yaml
URL: http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/conf/cassandra.yaml?rev=1081586&r1=1081585&r2=1081586&view=diff
==============================================================================
--- cassandra/branches/cassandra-0.7/conf/cassandra.yaml (original)
+++ cassandra/branches/cassandra-0.7/conf/cassandra.yaml Mon Mar 14 22:19:10 2011
@@ -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



Mime
View raw message