hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9953) PerformanceEvaluation: Decouple data size from client concurrency
Date Fri, 25 Apr 2014 15:50:16 GMT

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

Nick Dimiduk commented on HBASE-9953:
-------------------------------------

[~jmspaggi]

bq. 2) If both (opts.size == DEFAULT_OPTS.size) and (opts.perClientRunRows == DEFAULT_OPTS.perClientRunRows)
then opts.totalRows is never set?

Yes, that's fine; in this case the default totalRows value of 1024 * 1024 is used.

> PerformanceEvaluation: Decouple data size from client concurrency
> -----------------------------------------------------------------
>
>                 Key: HBASE-9953
>                 URL: https://issues.apache.org/jira/browse/HBASE-9953
>             Project: HBase
>          Issue Type: Test
>          Components: test
>            Reporter: Nick Dimiduk
>            Priority: Minor
>         Attachments: HBASE-9953.00.patch, HBASE-9953.01.patch
>
>
> PerfEval tool provides a {{--rows=R}} for specifying the number of records to work with
and requires the user provide a value of N, used as the concurrency level. From what I can
tell, every concurrent process will interact with R rows. In order to perform an apples-to-apples
test, the user must re-calculate the value R for every new value of N.
> Instead, I propose accepting a {{--size=S}} for the amount of data to interact with and
let PerfEval divide that amongst the N clients on the user's behalf.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message