You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Marc Spaggiari (JIRA)" <ji...@apache.org> on 2013/11/12 04:08:18 UTC

[jira] [Commented] (HBASE-9953) PerformanceEvaluation: Decouple data size from client concurrency

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

Jean-Marc Spaggiari commented on HBASE-9953:
--------------------------------------------

-1 for --size instead of --rows
+1 for --size in addition of --rows 

;)

I think the 2 can (and need to) leave together so we can still easily compare previous release to new release.

> 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
>
> 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.1#6144)