cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6726) Recycle CompressedRandomAccessReader/RandomAccessReader buffers independently of their owners, and move them off-heap when possible
Date Tue, 19 Aug 2014 06:04:18 GMT

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

Benedict commented on CASSANDRA-6726:
-------------------------------------

[~jbellis] I'd be inclined to include this patch in 2.1.1, otherwise we're unlikely to see
much benefit from it, as I fully expect the new file format to not use these classes at all
(and maybe not even the old format in 3.0, if we deliver an in process page cache)

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

Mime
View raw message