cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5521) move IndexSummary off heap
Date Wed, 01 May 2013 23:56:15 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647094#comment-13647094
] 

Pavel Yaskevich commented on CASSANDRA-5521:
--------------------------------------------

if we do so we would have to change partitioner interface to decorateKey and getToken, DecoratedKey
to have two "key" fields and change at least MurmurHash to accept both BB and M at the same
time. I'm my opinion it's just too many changes just because we don't require JNA but with
hybrid approach we don't have to do any of that work. Besides mentioned users would want to
run with JNA in production anyway.
                
> 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

Mime
View raw message