Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 25 Apr 2014 15:48:15 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12678705.1384215202231.181603.1398440895803@arcas>
In-Reply-To: <JIRA.12678705.1384215202231@arcas>
References: <JIRA.12678705.1384215202231@arcas>
Subject: [jira] [Updated] (HBASE-9953) PerformanceEvaluation: Decouple data
 size from client concurrency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk updated HBASE-9953:
--------------------------------

    Attachment: HBASE-9953.01.patch

Refreshing patch after a short hiatus. Added description for new --size command to help text.

> 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)