Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 25 Apr 2017 23:07:04 +0000 (UTC)
From: "Dikang Gu (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13066883.1493161606000.49551.1493161624146@Atlassian.JIRA>
In-Reply-To: <JIRA.13066883.1493161606000@Atlassian.JIRA>
References: <JIRA.13066883.1493161606000@Atlassian.JIRA> <JIRA.13066883.1493161606029@jira-lw-us.apache.org>
Subject: [jira] [Created] (CASSANDRA-13474) Cassandra pluggable storage
 engine
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 25 Apr 2017 23:07:09 -0000

Dikang Gu created CASSANDRA-13474:
-------------------------------------

             Summary: Cassandra pluggable storage engine
                 Key: CASSANDRA-13474
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13474
             Project: Cassandra
          Issue Type: New Feature
            Reporter: Dikang Gu


We did some experiment to switch Cassandra's storage engine to RocksDB.

In the experiment, I built a prototype to integrate Cassandra 3.0.12 and RocksDB on single column (key-value) use case, shadowed one of our production use case, and saw about 4-6X P99 read latency drop during peak time, compared to 3.0.12. Also, the P99 latency became more predictable as well.

Here is detailed note with more metrics: 

https://docs.google.com/document/d/1Ztqcu8Jzh4USKoWBgDJQw82DBurQmsV-PmfiJYvu_Dc/edit?usp=sharing 

I think the biggest latency win comes from we get rid of most Java garbages created by current read/write path and compactions, which reduces the JVM overhead and makes the latency to be more predictable.

We are very excited about the potential performance gain. As the next step, I propose to make the Cassandra storage engine to be pluggable (like Mysql and MongoDB), and we are very interested in providing RocksDB as one storage option with more predictable performance, together with community. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)