You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Y. SREENIVASULU REDDY (Jira)" <ji...@apache.org> on 2020/08/11 06:00:00 UTC

[jira] [Comment Edited] (HBASE-24850) CellComparator perf improvement

    [ https://issues.apache.org/jira/browse/HBASE-24850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175260#comment-17175260 ] 

Y. SREENIVASULU REDDY edited comment on HBASE-24850 at 8/11/20, 5:59 AM:
-------------------------------------------------------------------------

Thanks [~anoop.hbase] for addressing this issue.

[~ram_krish]  I have updated the test results for MapReduce job also in the Jira https://issues.apache.org/jira/browse/HBASE-24754


was (Author: sreenivasulureddy):
Thanks [~anoop.hbase] for addressing this issue.

I have updated the test results for MapReduce job also in the Jira https://issues.apache.org/jira/browse/HBASE-24754

> 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)