gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alfonso Nishikawa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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
Date Fri, 03 Jan 2014 10:21:50 GMT

     [ https://issues.apache.org/jira/browse/GORA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alfonso Nishikawa updated GORA-117:
-----------------------------------

    Attachment: GORA-117.patch

Let's push this, then.

Uploaded proposal GORA-117.patch.
Can anyone check it with goraci? I don't have it configured and I am quite busy to use it
for my first time :P
Tests passes without problem, but I don't know if it works as expected.

It adds the option to gora.properties:
{code}
gora.hbasestore.scanner.caching=1000
{code}
with default value 0.

> 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
>
>         Attachments: GORA-117.patch
>
>
> 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)

Mime
View raw message