[
https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194147#comment-16194147
]
ramkrishna.s.vasudevan commented on HBASE-16417:
------------------------------------------------
I read the doc first not seen the patch yet.
So since these are in-memory compactions the effect of HDD/SSDs does it come
from the fact as how fast these segments in the pipeline are released after
flushes?
As said in the doc scans are affected if the number of segments in pipeline are
more and so is the case with flushes also which needs to read the segments?
Because here we capture the throughput of writes and flushes are not in the hot
path so does it mean that we get blocking updates and the throughput depends on
how fast the blocking udpates are cleared and that depends on the segment count?
> 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
> Fix For: 3.0.0
>
> Attachments: HBASE-16417.01.patch, HBASE-16417 - Adaptive Compaction
> Policy - 20171001.pdf, 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 - parameter tuning -
> 20171001.pdf, HBASE-16417-V01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
