Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 15 Apr 2014 12:39:15 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12708510.1397565530321.117121.1397565555749@arcas>
In-Reply-To: <JIRA.12708510.1397565530321@arcas>
References: <JIRA.12708510.1397565530321@arcas>
Subject: [jira] [Created] (CASSANDRA-7039) DirectByteBuffer compatible LZ4
 methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Benedict created CASSANDRA-7039:
-----------------------------------

             Summary: DirectByteBuffer compatible LZ4 methods
                 Key: CASSANDRA-7039
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7039
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Benedict
            Priority: Minor


As we move more things off-heap, it's becoming more and more essential to be able to use DirectByteBuffer (or native pointers) in various places. Unfortunately LZ4 doesn't currently support this operation, despite being JNI based - this means we both have to perform unnecessary copies to de/compress data from DBB, but also we can stall GC as any JNI method operating over a java array using the GetPrimitiveArrayCritical enters a critical section that prevents GC for its duration. This means STWs will be at least as long any running compression/decompression (and no GC will happen until they complete, so it's additive).

We should temporarily fork (and then resubmit upstream) jpountz-lz4 to support operating over a native pointer, so that we can pass a DBB or a raw pointer we have allocated ourselves. This will help improve performance when flushing the new offheap memtables, as well as enable us to implement CASSANDRA-6726 and finish CASSANDRA-4338.


--
This message was sent by Atlassian JIRA
(v6.2#6252)