hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4434) seek optimization: don't do eager HFile Scanner next() unless the next KV is needed
Date Sat, 24 Sep 2011 06:08:26 GMT

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

Hudson commented on HBASE-4434:
-------------------------------

Integrated in HBase-TRUNK #2247 (See [https://builds.apache.org/job/HBase-TRUNK/2247/])
    HBASE-4434 seek optimization: don't do eager HFile Scanner next() unless the next KV is
needed

stack : 
Files : 
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileScanner.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestBlocksRead.java


> seek optimization: don't do eager HFile Scanner next() unless the next KV is needed
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-4434
>                 URL: https://issues.apache.org/jira/browse/HBASE-4434
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Kannan Muthukkaruppan
>            Assignee: Kannan Muthukkaruppan
>             Fix For: 0.92.0
>
>         Attachments: HBASE-4434.txt
>
>
> When a seek/reseek is done on StoreFileScanner, in addition to setting the current KV,
it also does a HFileScanner level next() ahead of time even if the next KV is never actually
required. This inefficiency can potentially result in additional disk seeks and sub-optimal
use of the block cache (primarily for cases where the KVs are large and each occupies an HFile
block of its own).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message