Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "MemtableThresholds" page has been changed by FlipKromer. The comment on this change is: Note: in version 0.7b2+, the value will be applied on a per column-family basis. . http://wiki.apache.org/cassandra/MemtableThresholds?action=diff&rev1=17&rev2=18 -------------------------------------------------- If left unconfigured (missing from the config), this defaults to 128MB. - ''Note: The value is applied on a per column-family basis.'' + ''Note: in version 0.7b2+, the value will be applied on a [[https://issues.apache.org/jira/browse/CASSANDRA-1007|per column-family basis]].'' === MemtableObjectCountInMillions === This directive sets a threshold on the number of columns stored. Left unconfigured (missing from the config), this defaults to 0.1 (or 100,000 objects). The config file's inital setting of 0.3 (or 300,000 objects) is a conservative starting point. - ''Note: The value is applied on a per column-family basis.'' + ''Note: in version 0.7b2+, the value will be applied on a [[https://issues.apache.org/jira/browse/CASSANDRA-1007|per column-family basis]].'' + + == Using Jconsole To Optimize Thresholds == Cassandra's column-family mbeans have a number of attributes that can prove invaluable in determining optimal thresholds. One way to access this instrumentation is by using Jconsole, a graphical monitoring and management application that ships with your JDK.
