[
https://issues.apache.org/jira/browse/HBASE-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185023#comment-14185023
]
zhangduo commented on HBASE-10201:
----------------------------------
oh, I think there is a trick to optimize it.
In most case, store.setSeqIdOfOldestEdit(seqId) will not change the value of
seqIdOfOldestEdit because the sequence id is increase and we need to record the
smallest one.
maybe we can record current sequence id before appendNoSync, and compare it
with seqIdOfOldestEdit, if it is already larger than seqIdOfOldestEdit then we
can skip the setSeqIdOfOldestEdit call because the actual sequence id must be
larger than current sequence id value.
> Port 'Make flush decisions per column family' to trunk
> ------------------------------------------------------
>
> Key: HBASE-10201
> URL: https://issues.apache.org/jira/browse/HBASE-10201
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Attachments: 3149-trunk-v1.txt, HBASE-10201-0.98.patch,
> HBASE-10201-0.98_1.patch, HBASE-10201-0.98_2.patch, HBASE-10201.patch
>
>
> Currently the flush decision is made using the aggregate size of all column
> families. When large and small column families co-exist, this causes many
> small flushes of the smaller CF. We need to make per-CF flush decisions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
