Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "StorageConfiguration" page has been changed by tuxracer69. http://wiki.apache.org/cassandra/StorageConfiguration?action=diff&rev1=5&rev2=6 -------------------------------------------------- {{{ <MemtableObjectCountInMillions>0.1</MemtableObjectCountInMillions> + }}} + + + ''[New in 0.5'' + + The maximum time to leave a dirty memtable unflushed. + (While any affected columnfamilies have unflushed data from a + commit log segment, that segment cannot be deleted.) + This needs to be large enough that it won't cause a flush storm + of all your memtables flushing at once because none has hit + the size or count thresholds yet. For production, a larger + value such as 1440 is recommended. + + {{{ + <MemtableFlushAfterMinutes>60</MemtableFlushAfterMinutes> + }}} + '']'' Unlike most systems, in Cassandra writes are faster than reads, so you can afford more of those in parallel. A good rule of thumb is 2 concurrent reads per processor core. Increase {{{ConcurrentWrites}}} to the number of clients writing at once if you enable {{{CommitLogSync + CommitLogSyncDelay}}}.
