[
https://issues.apache.org/jira/browse/HBASE-24742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157774#comment-17157774
]
Lars Hofhansl edited comment on HBASE-24742 at 7/15/20, 12:43 AM:
------------------------------------------------------------------
There are two observations:
1. We do not need to check for "fake" keys inserted by the ROWCOL BF logic if
there are not ROWCOL BFs (or if they are not used)
2. We can extend the identity-compare of the nextIndexedKey across multiple
calls. It's just an optimization and not for correctness.
was (Author: lhofhansl):
There are two observations:
1. We do not need to check for "fake" keys inserted by the ROWCOL BF logic if
there are not ROWCOL BFs (or if they are not used)
2. We can extend the identify compare of the nextIndexedKey across multiple
calls. It's just an optimization and not for correctness.
> Improve performance of SKIP vs SEEK logic
> -----------------------------------------
>
> Key: HBASE-24742
> URL: https://issues.apache.org/jira/browse/HBASE-24742
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Attachments: hbase-24742-branch-1.txt
>
>
> In our testing of HBase 1.3 against the current tip of branch-1 we saw a 30%
> slowdown in scanning scenarios.
> We tracked it back to HBASE-17958 and HBASE-19863.
> Both add comparisons to one of the tightest HBase has.
> [~bharathv]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
