[
https://issues.apache.org/jira/browse/HBASE-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795464#comment-13795464
]
Vladimir Rodionov commented on HBASE-9769:
------------------------------------------
>From dev-hbase list:
{code}
Simple table: one column + one qualifier
Two type of scans:
1. Scan.addFamily(CF)
2. Scan.addColumn(CF, CQ)
Both run on block cache (all data in memory)
Tested on StoreScanner directly.
1. 4.2M KVs per sec per one thread
2. 1.5M KVs per second per one thread.
The difference? First scanner's ScanQueryMatcher returns INCLUDE, DONE, second
- INCLUDE_NEXT_ROW, DONE
The cost of Row's reseek is huge.
{code}
> Improve Scanner with explicit column list performance when rows are
> small/medium size
> -------------------------------------------------------------------------------------
>
> Key: HBASE-9769
> URL: https://issues.apache.org/jira/browse/HBASE-9769
> Project: HBase
> Issue Type: Improvement
> Components: Scanners
> Affects Versions: 0.98.0, 0.94.12, 0.96.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
