Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <12902101.337201281726137163.JavaMail.jira@thor>
Date: Fri, 13 Aug 2010 15:02:17 -0400 (EDT)
From: "ryan rawson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Updated: (HBASE-2914) Profiling indicates that
 ThriftUtilities.rowResultFromHBase is quite inefficient
In-Reply-To: <2959274.337161281726136391.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ryan rawson updated HBASE-2914:
-------------------------------

    Attachment: HBASE-2914.patch

this patch is against the branch but it should hopefully apply to trunk w/o much trouble

> Profiling indicates that ThriftUtilities.rowResultFromHBase is quite inefficient
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-2914
>                 URL: https://issues.apache.org/jira/browse/HBASE-2914
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.6, 0.89.20100621
>            Reporter: ryan rawson
>            Assignee: ryan rawson
>             Fix For: 0.90.0
>
>         Attachments: HBASE-2914.patch
>
>
> Profiling of ThriftServer here at SU has indicated that the call ThriftUtilities.rowResultFromHBase() is quite inefficient.  It first calls Result.getRowResult() which is inefficient and slow. Instead by reimplementing to create the TRowResult (the thrift return type) straight from the KeyValue[] array the performance boost is substantial, reducing time serializing the results.  In my profiling the time spent in scannerGetList() went from 1100ms to 108ms on similar test runs.  

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