Re: Cassandra on RocksDB experiment result

> Please take a look and let me know your thoughts. 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. > I want to put this here for the

Re: unsubscribe

unsubscribe On Wed, Apr 5, 2017 at 1:35 AM, 郑蒙家(蒙家) wrote: > unsubscribe

Guidelines on testing

About a month ago, in the ‘Code quality, principles and rules’ thread, I’d proposed adding some testing standards to the project in lieu of revisiting the idea of removing singletons. The idea was that we could drive incremental improvement of the test coverage and testability situation that

Re: Cassandra on RocksDB experiment result

Dikang, First I want to thank you and everyone else at Instragram for the engineering talent you have devoted to the Cassandra project. Here's yet another great example. He's going to hate me for dragging him into this, but Vijay Parthasarathy has done some exploratory work before on integrating

Re: Cassandra on RocksDB experiment result

unsubscribe On Sun, Apr 23, 2017 at 4:25 PM, Nate McCall wrote: > > Please take a look and let me know your thoughts. 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

Re: Cassandra on RocksDB experiment result

Thanks everyone for the feedback and suggestions! They are all very helpful. I'm looking forward to having more discussions about the implementation details. As the next step, we will be focus on three areas: 1. Pluggable storage engine interface. 2. Wide column support on RocksDB. 3. Streaming