Edward Bortnikov commented on HBASE-14920:

Good catch [~devaraj]. We've started working on a user-facing blog, see the 
write-up in 
 Would be great to hear from everyone what you think about the content. 

The reason we did not publish the blog post yet is that we are doing extensive 
performance testing of the feature literally these days. The preliminary 
results demonstrated at HBaseCon were very good but now we're working with 100X 
data, so the benchmarks take a while. One more thing we'd like to finalize is 
the in-memory compaction policy which we'd like to see automated as much as 
possible (right now there's just one configuration parameter but maybe it's 
possible to avoid it too).   

Pushing to get all done before the end-of-year, both to enable the optimization 
standalone and to remove barriers to off-heaping the write path.

Thanks [~devaraj].  

> Compacting Memstore
> -------------------
>                 Key: HBASE-14920
>                 URL: https://issues.apache.org/jira/browse/HBASE-14920
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Eshcar Hillel
>            Assignee: Eshcar Hillel
>             Fix For: 2.0.0
>         Attachments: HBASE-14920-V01.patch, HBASE-14920-V02.patch, 
> HBASE-14920-V03.patch, HBASE-14920-V04.patch, HBASE-14920-V05.patch, 
> HBASE-14920-V06.patch, HBASE-14920-V07.patch, HBASE-14920-V08.patch, 
> HBASE-14920-V09.patch, HBASE-14920-V10.patch, move.to.junit4.patch
> Implementation of a new compacting memstore with non-optimized immutable 
> segment representation

This message was sent by Atlassian JIRA

Reply via email to