[
https://issues.apache.org/jira/browse/CASSANDRA-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103226#comment-14103226
]
Benedict commented on CASSANDRA-6726:
-------------------------------------
It could have significant impact on very specific workloads. Any in memory
workloads with many files (e.g. two levels of LCS that fit in memory) and many
concurrent readers could well create a _lot_ of file opening/closing under the
current scheme, which would have a pronounced impact. Gut feeling is that is
borderline common enough to include, but since borderline I'm certainly
comfortable closing as Won't Fix, superceded by CASSANDRA-5863
> Recycle CompressedRandomAccessReader/RandomAccessReader 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: Branimir Lambov
> Priority: Minor
> Labels: performance
> Fix For: 3.0
>
> Attachments: cassandra-6726.patch
>
>
> 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.2#6252)
