hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10047) postScannerFilterRow consumes a lot of CPU in tall table scans
Date Sun, 22 Dec 2013 05:05:52 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Lars Hofhansl updated HBASE-10047:

    Attachment: 10047-0.94-poc-v3.txt

New patch. 100% untested. Checks:
# the interface was implemented directly
# the any class up the chain either has the hook directly, or BaseRegionCoprocessor is reached.

This is getting a bit out of hand.
Also not sure whether I can do the == comparison between the classes, they might come from
the different class loaders
(I think... It might also be the case that BaseRegionObserver is always loaded via the system
class loader).
Then it would need tests to make sure it does the right thing in all situations, etc, etc.

I think I'm just going to close this.

> postScannerFilterRow consumes a lot of CPU in tall table scans
> --------------------------------------------------------------
>                 Key: HBASE-10047
>                 URL: https://issues.apache.org/jira/browse/HBASE-10047
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>         Attachments: 10047-0.94-poc-v3.txt, 10047-0.94-sample-v2.txt, 10047-0.94-sample.txt,
> Continuing my profiling quest, I find that in scanning tall table (and filtering everything
on the server) a quarter of the time is now spent in the postScannerFilterRow coprocessor

This message was sent by Atlassian JIRA

View raw message