You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2013/02/10 20:21:12 UTC

[jira] [Commented] (HBASE-7803) Look into REST API performance

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

Andrew Purtell commented on HBASE-7803:
---------------------------------------

Have you considered HTTP overheads? YCSB throws s lot of ops at the target and I'd guess in your testing each read is a separate HTTP request. This was a topic that came up around the time of REST's introduction. It is appropriate for bulk or infrequent ops ("wide" load) as opposed to hundreds or thousands of transactions per second ("tall" load). For tall load, use Thrift or the native API. REST does hatching for scanners and supports bundling ops into a single HTTP transaction to amortize the HTTP overheads.

                
> Look into REST API performance
> ------------------------------
>
>                 Key: HBASE-7803
>                 URL: https://issues.apache.org/jira/browse/HBASE-7803
>             Project: HBase
>          Issue Type: Task
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>
> I have a YCSB client using the REST API.  My testing shows the performance for scan with REST API is much worse than that with the java client API.  We need to look into it and find out the root cause, either the test issue, or our REST API issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira