[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

["Otis Gospodnetic (JIRA)" <ji...@apache.org>]

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

Otis Gospodnetic commented on GORA-117:
---------------------------------------

Should this get committed?  I see [~jnioche] mentioned this in the Nutch draft for the board...  Thanks.


> 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: gora-hbase
>    Affects Versions: 0.2
>            Reporter: Eric Newton
>            Assignee: stack
>             Fix For: 0.4
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)