[ 
https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eshcar Hillel updated HBASE-16417:
----------------------------------
    Fix Version/s: 2.0.0
     Release Note: 
A new memstore compaction policy: Adaptive.
Adaptive compaction adapts to the workload. It applies either index compaction 
or data compaction based on the ratio of redundant cells.

New configuration properties:
(1) hbase.hregion.compacting.memstore.adaptive.compaction.threshold
sets the threshold on the fraction of redundant cells to trigger memstore data 
compaction.
Default value is 0.5.

(2) hbase.hregion.compacting.memstore.adaptive.compaction.probability
sets the initial probability of applying data compaction (a throttling 
parameter). Default value is 0.5.

In addition 
- changes the default value of the configuration property 
hbase.memstore.inmemoryflush.threshold.factor to 0.02 (previously 0.25)
 - changes the default value of the configuration property 
hbase.hregion.compacting.pipeline.segments.limit to 4 (previously 1)

> In-Memory MemStore Policy for Flattening and Compactions
> --------------------------------------------------------
>
>                 Key: HBASE-16417
>                 URL: https://issues.apache.org/jira/browse/HBASE-16417
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anastasia Braginsky
>            Assignee: Eshcar Hillel
>            Priority: Major
>             Fix For: 2.0.0, 3.0.0
>
>         Attachments: HBASE-16417 - Adaptive Compaction Policy - 20171001.pdf, 
> HBASE-16417 - parameter tuning - 20171001.pdf, HBASE-16417-V01.patch, 
> HBASE-16417-benchmarkresults-20161101.pdf, 
> HBASE-16417-benchmarkresults-20161110.pdf, 
> HBASE-16417-benchmarkresults-20161123.pdf, 
> HBASE-16417-benchmarkresults-20161205.pdf, 
> HBASE-16417-benchmarkresults-20170309.pdf, 
> HBASE-16417-benchmarkresults-20170317.pdf, HBASE-16417.01.patch, 
> HBASE-16417.02.patch, HBASE-16417.03.patch, HBASE-16417.04.patch, 
> HBASE-16417.05.patch, HBASE-16417.06.patch, HBASE-16417.07.patch, 
> HBASE-16417.07.patch, HBASE-16417.08.patch, HBASE-16417.09.patch, 
> HBASE-16417.10.patch, HBASE-16417.11.patch, HBASE-16417.12.patch, 
> HBASE-16417.13.patch, HBASE-16417.14.patch, HBASE-16417.15.patch, 
> HBASE-16417.16.patch, HBASE-16417.17.patch, HBASE-16417.17.patch, 
> HBASE-16417.17.patch, HBASE-16417.17.patch, HBASE-16417.17.patch, 
> HBASE-16417.18.patch, HBASE-16417.branch-2.17.patch
>
>
> This Jira explores the performance of different memstore compaction policies.
> It presents the result of write-only workload evaluation as well as read 
> performance in read-write workloads.
> We investigate several settings of hardware (SSD, HDD), key distribution 
> (Zipf, uniform), with multiple settings of the system, and compare measures 
> like write throughput, read latency, write volume, total gc time, etc.
> The submitted patch sets some system properties at the values yielding 
> optimal performance. In addition we suggest a new Adaptive memstore 
> compaction policy that shows good tradeoffs between write throughput and 
> write volume.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to