[
https://issues.apache.org/jira/browse/HBASE-24850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175246#comment-17175246
]
ramkrishna.s.vasudevan commented on HBASE-24850:
------------------------------------------------
Thanks for raising this. I was waiting for [~sreenivasulureddy] to check the
other MR based change before I could raise a JIRA.
I did add a KV only path in the CellComparator like the BBKV path and that
helps a lot. And we get good numbers like the other Patch in
https://issues.apache.org/jira/browse/HBASE-24754
This is critical in the write to the memstore case and a flush case where we
will do a read from memstore. Currently memstore is pure KV only path.
> CellComparator perf improvement
> -------------------------------
>
> Key: HBASE-24850
> URL: https://issues.apache.org/jira/browse/HBASE-24850
> Project: HBase
> Issue Type: Improvement
> Components: Performance, scan
> Affects Versions: 2.0.0
> Reporter: Anoop Sam John
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.4.0
>
>
> We have multiple perf issues in 2.x versions compared to 1.x. Eg:
> HBASE-24754, HBASE-24637.
> The pattern is clear that where ever we do more and more Cell compares, there
> is some degrade. In HBASE-24754, with an old KVComparator style comparator,
> we see much better perf for the PutSortReducer. (Again the gain is huge
> because of large number of compare ops that test is doing). This issue is to
> address and optimize compares generally in CellComparatorImpl itself.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)