[
https://issues.apache.org/jira/browse/HBASE-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080582#comment-13080582
]
Ted Yu commented on HBASE-3855:
-------------------------------
This happened in TRUNK as well:
https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/lastCompletedBuild/testReport/org.apache.hadoop.hbase.regionserver/TestHRegion/testWritesWhileGetting/
> 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
> Priority: Blocker
> Fix For: 0.92.0
>
> Attachments: memstoreReseek.txt, memstoreReseek2.txt
>
>
> 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
