You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2014/08/21 01:45:29 UTC

[jira] [Commented] (HBASE-11792) Organize PerformanceEvaluation usage output

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

Nick Dimiduk commented on HBASE-11792:
--------------------------------------

Ping [~misty] in case you're interested in getting into the code a little.

> Organize PerformanceEvaluation usage output
> -------------------------------------------
>
>                 Key: HBASE-11792
>                 URL: https://issues.apache.org/jira/browse/HBASE-11792
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance, test
>            Reporter: Nick Dimiduk
>            Priority: Minor
>              Labels: beginner
>
> PerformanceEvaluation has enjoyed a good bit of attention recently. All the new features are muddled together. It would be nice to organize the output of the Options list according to some scheme. I was thinking you're group entries by when they're used. For example
> *General options*
> - nomapred
> - rows
> - oneCon
> - ...
> *Table Creation/Write tests*
> - compress
> - flushCommits
> - valueZipf
> - ...
> *Read tests*
> - filterAll
> - multiGet
> - replicas
> - ...



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