hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sishen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-887) Fix a hotspot in scanners
Date Sun, 19 Oct 2008 17:24:50 GMT

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

sishen commented on HBASE-887:
------------------------------

Should we add the api to get multiple rows once depends on User's choice in HTable#ClientScanner?

Now the api is public RowResult next() throws IOException;

It will try to get HTable.this.scannerCaching at once.

Is this meaningful to add the method

public RowResult[] next(int nbRows) throws IOException;

> Fix a hotspot in scanners
> -------------------------
>
>                 Key: HBASE-887
>                 URL: https://issues.apache.org/jira/browse/HBASE-887
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client, regionserver
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.19.0
>
>         Attachments: 877-chart.jpg, hbase-887-v1.patch, Scanning Benchmarks.pdf
>
>
> When scanning, we do a lot of RPCs and this has a huge performance hit. I propose that
we add a way to fetch more rows during next() and put them in cache. This should be configurable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message