[
https://issues.apache.org/jira/browse/HBASE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852663#comment-13852663
]
Lars Hofhansl commented on HBASE-10047:
---------------------------------------
Trying with Phoenix I do see a 5-10% improvement when doing a count(1) on a
tall table (1 col).
Scanning the same (1 col) table with the HBase client using a Filter to filter
all data at the server I see 25% scan improvement with patch.
The question is whether the extra complexity in the code is worth it.
[~apurtell], any opinion?
> 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.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)
