You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ryan rawson (JIRA)" <ji...@apache.org> on 2010/09/22 21:56:35 UTC

[jira] Updated: (HBASE-2914) Profiling indicates that ThriftUtilities.rowResultFromHBase is quite inefficient

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

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

        Status: Resolved  (was: Patch Available)
    Resolution: Duplicate

already fixed in trunk!

> 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.