You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Jim Apple (JIRA)" <ji...@apache.org> on 2017/11/11 23:08:01 UTC

[jira] [Resolved] (IMPALA-6150) Clarify order of arguments to single_node_perf_run.py

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

Jim Apple resolved IMPALA-6150.
-------------------------------
    Resolution: Fixed

https://gerrit.cloudera.org/#/c/8470/

> Clarify order of arguments to single_node_perf_run.py
> -----------------------------------------------------
>
>                 Key: IMPALA-6150
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6150
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 2.11.0
>            Reporter: Tim Armstrong
>            Assignee: Jim Apple
>            Priority: Trivial
>
> The script help doesn't specify which of the hashes is the reference and which is the baseline, which makes it hard to interpret the output of the run. I'm not sure but I think I may have been interpreting the order backwards. Can we clarify this in the help?
> {noformat}
> $ ./bin/single_node_perf_run.py --help
> Usage: 
> single_node_perf_run.py [options] git_hash_A [git_hash_B]
> When one hash is given, measures the performance on the specified workloads.
> When two hashes are given, compares their performance. Output is in
> $IMPALA_HOME/perf_results/latest.
> WARNING: This script will run git checkout. You should not touch the tree
> while the script is running. You should start the script from a clean git
> tree.
> WARNING: When --load is used, this script calls load_data.py which can
> overwrite your TPC-H and TPC-DS data.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)