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

Lars Hofhansl commented on HBASE-9000:
--------------------------------------

bq. 'reseek to next row' gets slower with patch.

This is because the limit of 20 not optimal for this particular case. We'll 
never get it 100% right for all cases, what we need to do is to avoid the worst 
cases. In this case it'll be faster per op if the limit is increased to 30 (my 
guess) or lowered.


> Linear reseek in Memstore
> -------------------------
>
>                 Key: HBASE-9000
>                 URL: https://issues.apache.org/jira/browse/HBASE-9000
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.89-fb
>            Reporter: Shane Hogan
>            Priority: Minor
>             Fix For: 0.89-fb
>
>         Attachments: hbase-9000-benchmark-program.patch, 
> hbase-9000-port-fb.patch
>
>
> This is to address the linear reseek in MemStoreScanner. Currently reseek 
> iterates over the kvset and the snapshot linearly by just calling next 
> repeatedly. The new solution is to do this linear seek up to a configurable 
> maximum amount of times then if the seek is not yet complete fall back to 
> logarithmic seek.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to