[
https://issues.apache.org/jira/browse/HBASE-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981952#comment-13981952
]
Hudson commented on HBASE-9953:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK #5120 (See
[https://builds.apache.org/job/HBase-TRUNK/5120/])
HBASE-9953 PerformanceEvaluation: Decouple data size from client concurrency
(ndimiduk: rev 1590216)
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java
> 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: Performance
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 0.99.0
>
> 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)
