[
https://issues.apache.org/jira/browse/HBASE-24850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249533#comment-17249533
]
ramkrishna.s.vasudevan commented on HBASE-24850:
------------------------------------------------
The branching and the parsing of the cells parts are both the reasons.
In 1.3.x we don't do branching (as only one cell type is available)but we are
not parsing the cell parts indvidually. So that causes a performance issue.
In 2.x we do branching and also don't do parsing. So it is having more impact.
Now in the recent patch we do the parsing so it becomes faster but also in the
branching we remove branches getting created again like inside compareRows,
compareFam, compareCols etc. That helps. There is also a reason why the bulk
load perf is slower based on these factors.
> 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: 3.0.0-alpha-1, 2.5.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)
