[
https://issues.apache.org/jira/browse/HBASE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854409#comment-13854409
]
Lars Hofhansl commented on HBASE-10047:
---------------------------------------
Interesting, didn't realize that can happen. After the region is loaded? Ohh,
when we detect an error we remove the coprocessor.
SortedCopyOnWriteSet should have been a hint too :)
The first patch is still valid, since we're only removing after the region was
loaded.
I didn't measure any perf improvement with v2 anyway, it seems instanceof is
not the issue.
> 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-sample-v2.txt, 10047-0.94-sample.txt,
> postScannerFilterRow.png
>
>
> 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 hook.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
