Thanks everyone! @Kyrylo, In Rocksandra world, the storage engine is built on top of RocksDB, which is another LSM tree based storage engine. So the immutable sstables and compactions are managed by RocksDB instances. RocksDB supports different compaction strategies, similar to STCS and LCS. The compactions are managed by C++, so it will not generate any pressure to JVM.
@Romain, Thanks, and Rocksandra is not limited to only support key/value data model. We support most of the data types and table data model in Cassandra. Dikang. On Tue, Mar 6, 2018 at 1:48 AM, Romain Hardouin <romainh...@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_lebed...@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 <dikan...@gmail.com> > *Sent:* Monday, March 5, 2018 8:26 PM > *To:* d...@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 > > -- Dikang
