[
https://issues.apache.org/jira/browse/CASSANDRA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920328#comment-13920328
]
Pavel Yaskevich commented on CASSANDRA-6689:
--------------------------------------------
So the only question that I still have - what is the main goal of the ticket?
Is it to move to zero copy for memtables or minimize number of allocations on
java heap? If it's the latter then I don't see why we can't have separate
allocator for memtable and use a separate allocator for operations which would
do a copy from memtable memory, that way we don't have to track as such as we
do right now and allocator interface is going to be better encapsulated
(basically expose alloc/release), I'm not sure if we need sub pools or groups
of allocators in there, I really like how jemalloc and others do it also Netty
already has implementation of jemalloc (ByteBufAlloc) so maybe we can reuse
that?...
> Partially Off Heap Memtables
> ----------------------------
>
> Key: CASSANDRA-6689
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6689
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Fix For: 2.1 beta2
>
> Attachments: CASSANDRA-6689-small-changes.patch
>
>
> Move the contents of ByteBuffers off-heap for records written to a memtable.
> (See comments for details)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
