[
https://issues.apache.org/jira/browse/CASSANDRA-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict updated CASSANDRA-6726:
--------------------------------
Description: Whilst CRAR and RAR are pooled, we could and probably should
pool the buffers independently, so that they are not tied to a specific
sstable. It may be possible to move the RAR buffer off-heap, and the CRAR
sometimes (e.g. Snappy may possibly support off-heap buffers) (was: It seems
like this should be a reasonably easy and quick win.)
Issue Type: Improvement (was: Bug)
Summary: Recycle CRAR/RAR buffers independently of their owners, and
move them off-heap when possible (was: Recycle CompressedRandomAccessReader
and RandomAccessReader buffers, and move them off-heap)
> Recycle CRAR/RAR buffers independently of their owners, and move them
> off-heap when possible
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6726
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6726
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 2.1
>
>
> Whilst CRAR and RAR are pooled, we could and probably should pool the buffers
> independently, so that they are not tied to a specific sstable. It may be
> possible to move the RAR buffer off-heap, and the CRAR sometimes (e.g. Snappy
> may possibly support off-heap buffers)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
