You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/11/06 22:16:11 UTC
[jira] [Commented] (CASSANDRA-4478) Make index_interval be measured
in kb (instead of number of keys)
[ https://issues.apache.org/jira/browse/CASSANDRA-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994438#comment-14994438 ]
Robert Stupp commented on CASSANDRA-4478:
-----------------------------------------
Do we still need this? {{index_interval}} is only present as a deprecated and unused field in {{Config}} class.
> Make index_interval be measured in kb (instead of number of keys)
> -----------------------------------------------------------------
>
> Key: CASSANDRA-4478
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4478
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Priority: Minor
> Fix For: 3.x
>
> Attachments: 4478-incomplete.txt
>
>
> Currently, index_interval is measured in number of keys: how may keys before adding an entry to the index summary. After CASSANDRA-2319, each index entry also contains the columns index for the row, so index entry can be a bit bigger and of differing sizes. Measuring in number of keys is thus sub-optimal and difficult to tune, since you might want a different setting depending of whether your rows are big or small, but the setting is global.
> So we should move to measuring the interval in bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)