[
https://issues.apache.org/jira/browse/CASSANDRA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944214#comment-13944214
]
Benedict commented on CASSANDRA-6689:
-------------------------------------
bq. because people would find it and create a issue for that
My understanding (not my policy) is that this is explicitly not a default
supported option (in the current state of affairs) because of the expectation
of increased heap fragmentation and GC death spiral, which is why I'm happy
with the ugly name for that one option.
bq. I has thinking of thing as easy as replacing HeapAllocator.instance with
SlabAllocator.instance (which would only have a heap allocation enabled).
In this case what is to be gained? Seems likely it would only increase the need
for old gen collections, as we wouldn't be able to do any reuse?
> 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
> Labels: performance
> Fix For: 2.1 beta2
>
> Attachments: CASSANDRA-6689-final-changes.patch,
> 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)
