cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-5863) Create a Decompressed Chunk Cache
Date Wed, 18 Sep 2013 01:07:52 GMT


Jonathan Ellis edited comment on CASSANDRA-5863 at 9/18/13 1:06 AM:

Probably easier to just special case seq scans to not cache, the way we did with fadvise pre-CASSANDRA-4937.
      was (Author: jbellis):
    Probably easier to just special case seq scans to not cache, the way we [used to?] do
with fadvise.
> Create a Decompressed Chunk Cache
> ---------------------------------
>                 Key: CASSANDRA-5863
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: T Jake Luciani
>            Assignee: Tyler Hobbs
>             Fix For: 2.1
> Currently, for every read, the CRAR reads each compressed chunk into a byte[], sends
it to ICompressor, gets back another byte[] and verifies a checksum.  
> This process is where the majority of time is spent in a read request.  
> Before compression, we would have zero-copy of data and could respond directly from the
> It would be useful to have some kind of Chunk cache that could speed up this process
for hot data. Initially this could be a off heap cache but it would be great to put these
decompressed chunks onto a SSD so the hot data lives on a fast disk similar to

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message