You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2013/05/01 07:56:18 UTC
[jira] [Comment Edited] (CASSANDRA-5521) move IndexSummary off heap
[ https://issues.apache.org/jira/browse/CASSANDRA-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646352#comment-13646352 ]
Pavel Yaskevich edited comment on CASSANDRA-5521 at 5/1/13 5:55 AM:
--------------------------------------------------------------------
Have we considered using vint encoding on those arrays as we keep them in memory anyway to minimize space consumption?
Edit: i remember now why that is not a good idea :) I wonder though how what could memory footprint be if we use TreeMap inside and keys and offsets (in vint encoding) saved in native memory...
was (Author: xedin):
Have we considered using vint encoding on those arrays as we keep them in memory anyway to minimize space consumption?
> move IndexSummary off heap
> --------------------------
>
> Key: CASSANDRA-5521
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5521
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Vijay
> Fix For: 2.0
>
>
> IndexSummary can still use a lot of heap for narrow-row sstables. (It can also contribute to memory fragmentation because of the large arrays it creates.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira