[
https://issues.apache.org/jira/browse/HBASE-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029451#comment-13029451
]
dhruba borthakur commented on HBASE-3855:
-----------------------------------------
Thanks Mikhail for your comments.
let's keep this jira focussed only on memstore improvements. if we can do
better while seeking on disk, can we open a new JIRA for that one (and link it
to this one).
My use-case for this jira is for the situation when the entire scan request can
be satisfied from the memstore.
> Performance degradation of memstore because reseek is linear
> ------------------------------------------------------------
>
> Key: HBASE-3855
> URL: https://issues.apache.org/jira/browse/HBASE-3855
> Project: HBase
> Issue Type: Improvement
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Priority: Blocker
> Fix For: 0.94.0
>
>
> The scanner use reseek to find the next row (or next column) as part of a
> scan. The reseek code iterates over a Set to position itself at the right
> place. If there are many thousands of kvs that need to be skipped over, then
> the time-cost is very high. In this case, a seek would be far lesser in cost
> than a reseek.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
