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-8316) JoinedHeap for non essential column families should reseek instead of seek
Date Wed, 10 Apr 2013 23:27:18 GMT

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

Hudson commented on HBASE-8316:
-------------------------------

Integrated in HBase-0.94 #954 (See [https://builds.apache.org/job/HBase-0.94/954/])
    HBASE-8316 JoinedHeap for non essential column families should reseek instead of seek
(Revision 1466708)

     Result = SUCCESS
larsh : 
Files : 
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java

                
> JoinedHeap for non essential column families should reseek instead of seek
> --------------------------------------------------------------------------
>
>                 Key: HBASE-8316
>                 URL: https://issues.apache.org/jira/browse/HBASE-8316
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Filters, Performance, regionserver
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.98.0, 0.94.7, 0.95.1
>
>         Attachments: 8316-0.94.txt, 8316-trunk.txt, 8316-trunk.txt, FDencode.png, noencode.png
>
>
> This was raised by the Phoenix team. During a profiling session we noticed that catching
the joinedHeap up to the current rows via seek causes a performance regression, which makes
the joinedHeap only efficient when either a high or low percentage is matched by the filter.
> (High is fine, because the joinedHeap will not get behind as often and does not need
to be caught up, low is fine, because the seek isn't happening frequently).
> In our tests we found that the solution is quite simple: Replace seek with reseek. Patch
coming soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message