cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5020) Time to switch back to byte[] internally?
Date Wed, 12 Dec 2012 18:28:20 GMT

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

T Jake Luciani commented on CASSANDRA-5020:
-------------------------------------------

I thought the same but ByteBuffer is an abstract class :( we could build our own wrapper on
BB though...

I think the bigger win will be CASSANDRA-5019
                
> Time to switch back to byte[] internally?
> -----------------------------------------
>
>                 Key: CASSANDRA-5020
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5020
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 2.0
>
>
> We switched to ByteBuffer for column names and values back in 0.7, which gave us a short
term performance boost on mmap'd reads, but we gave that up when we switched to refcounted
sstables in 1.0.  (refcounting all the way up the read path would be too painful, so we copy
into an on-heap buffer when reading from an sstable, then release the reference.)
> A HeapByteBuffer wastes a lot of memory compared to a byte[] (5 more ints, a long, and
a boolean).
> The hard problem here is how to do the arena allocation we do on writes, which has been
very successful in reducing STW CMS from heap fragmentation.  ByteBuffer is a good fit there.

--
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