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

Kevin Risden edited comment on KNOX-1525 at 10/15/18 5:18 PM:
--------------------------------------------------------------

h2. Results

50 thousand rows
 * HBase shell - ~11.0 seconds
 * HBase Rest- ~1.6 seconds
 * HBase Rest with Knox - ~ seconds

100 thousand rows
 * HBase shell - ~13.9 seconds
 * HBase Rest- ~3.4 seconds
 * HBase Rest with Knox - ~ seconds

200 thousand rows
 * HBase shell - ~19.7 seconds
 * HBase Rest- ~5.3 seconds
 * HBase Rest with Knox - ~ seconds


was (Author: risdenk):
h2. Results

50 thousand rows
 * HBase shell - ~11.0 seconds
 * HBase Rest- ~ seconds
 * HBase Rest with Knox - ~ seconds

100 thousand rows
 * HBase shell - ~13.9 seconds
 * HBase Rest- ~ seconds
 * HBase Rest with Knox - ~ seconds

200 thousand rows
 * HBase shell - ~19.7 seconds
 * HBase Rest- ~ seconds
 * HBase Rest with Knox - ~ seconds

> HBase "scan" performance evaluation
> -----------------------------------
>
>                 Key: KNOX-1525
>                 URL: https://issues.apache.org/jira/browse/KNOX-1525
>             Project: Apache Knox
>          Issue Type: Task
>            Reporter: Kevin Risden
>            Assignee: Kevin Risden
>            Priority: Major
>             Fix For: 1.2.0
>
>
> While looking at WebHDFS performance in KNOX-1221, I decided to look a bit 
> more into performance for common use cases. HBase performance is another area 
> that could use some research.
> Use "scan limit" to get a comparison of raw return speed from HBase Rest. 
> This should show how fast results can be streamed through HBase Rest and 
> Knox. Compare the results to "hbase shell" since this will render the data 
> directly from HBase through the typical HBase shell. This should give 
> comparisons for the difference in overhead between HBase, HBase Rest and 
> HBase Rest with Knox.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to