You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gora.apache.org by "stack (Commented) (JIRA)" <ji...@apache.org> on 2012/04/11 01:43:17 UTC

[jira] [Commented] (GORA-117) gora hbase does not have a mechanism to set the caching on a scanner, which makes for poor performance on map/reduce jobs

    [ https://issues.apache.org/jira/browse/GORA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251184#comment-13251184 ] 

stack commented on GORA-117:
----------------------------

Let me have a go at making this at least configurable and start w/ something a little sensible.
                
> gora hbase does not have a mechanism to set the caching on a scanner, which makes for poor performance on map/reduce jobs
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GORA-117
>                 URL: https://issues.apache.org/jira/browse/GORA-117
>             Project: Apache Gora
>          Issue Type: Bug
>          Components: storage-hbase
>            Reporter: Eric Newton
>            Assignee: stack
>
> goraci runs a map/reduce job over all the data that it generates.  The hbase storage uses a scanner that doesn't cache rows, which means every fetch requires an RPC call.  I experimented with 
> scan.setCaching(1000);
> and goraci Verify ran about 30x faster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira