cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Mueller <carl.muel...@smartthings.com>
Subject Re: Rocksandra blog post
Date Tue, 06 Mar 2018 15:41:33 GMT
Basically they are avoiding gc, right? Not necessarily improving on the
theoreticals of sstables and LSM trees.

Why didn't they use/try scylla? I'd be interested to see that benchmark.

On Tue, Mar 6, 2018 at 3:48 AM, Romain Hardouin <romainh_ml@yahoo.fr.invalid
> wrote:

> Rocksandra is very interesting for key/value data model. Let's hope it
> will land in C* upstream in the near future thanks to pluggable storage.
> Thanks Dikang!
>
>
>
> Le mardi 6 mars 2018 à 10:06:16 UTC+1, Kyrylo Lebediev <
> Kyrylo_Lebediev@epam.com> a écrit :
>
>
> Thanks for sharing, Dikang!
>
> Impressive results.
>
>
> As you plugged in different storage engine, it's interesting how you're
> dealing with compactions in Rocksandra?
>
> Is there still the concept of immutable SSTables + compaction strategies
> or it was changed somehow?
>
>
> Best,
>
> Kyrill
>
> ------------------------------
> *From:* Dikang Gu <dikang85@gmail.com>
> *Sent:* Monday, March 5, 2018 8:26 PM
> *To:* dev@cassandra.apache.org; cassandra
> *Subject:* Rocksandra blog post
>
> As some of you already know, Instagram Cassandra team is working on the
> project to use RocksDB as Cassandra's storage engine.
>
> Today, we just published a blog post about the work we have done, and more
> excitingly, we published the benchmark metrics in AWS environment.
>
> Check it out here:
> https://engineering.instagram.com/open-sourcing-a-10x-
> reduction-in-apache-cassandra-tail-latency-d64f86b43589
>
> Thanks
> Dikang
>
>

Mime
View raw message