If you just want to benchmark the cluster it wont matter too much, though I would set keys_cached to 0 and increate memtable throughput to 64 or 128. If you are testing to get a better idea for your app then use similar settings to your app.
keys_cahced is the number of keys for concurrent_readers and concurrent_writers see the comments in cong/cassandra.yaml. I could not find this KS definition in the hector code base so not sure why they chose those values. Aaron On 9 Apr 2011, at 11:10, mcasandra wrote: > I am starting a stress test using hector on 6 node machine 4GB heap and 12 > core. In hectore readme this is what I got by default: > > create keyspace StressKeyspace > with replication_factor = 3 > and placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy'; > > use StressKeyspace; > drop column family StressStandard; > create column family StressStandard > with comparator = UTF8Type > and keys_cached = 10000 > and memtable_flush_after = 1440 > and memtable_throughput = 32; > > Are these good values? I was thinking of highher keys_cached but not sure if > it's in bytes or no of keys. > > Also not sure how to tune memtable values. > > I have set concurrent_readers to 32 and writers to 48. > > Can someone please help me with good values that I can start this test with? > > Also, any other suggested values that I need to change? > > Thanks > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/CF-config-for-Stress-Test-tp6255608p6255608.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
