You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Chao Sun (Jira)" <ji...@apache.org> on 2021/05/04 23:04:00 UTC

[jira] [Created] (SPARK-35315) Keep benchmark result consistent between spark-submit and SBT

Chao Sun created SPARK-35315:
--------------------------------

             Summary: Keep benchmark result consistent between spark-submit and SBT
                 Key: SPARK-35315
                 URL: https://issues.apache.org/jira/browse/SPARK-35315
             Project: Spark
          Issue Type: Improvement
          Components: Tests
    Affects Versions: 3.2.0
            Reporter: Chao Sun


Currently benchmark can be done in two ways: {{spark-submit}}, or SBT command. However in the former Spark will miss some properties such as {{IS_TESTING}}, which is useful to turn on/off some behavior like codegen. Therefore, the result could differ with the two methods. In addition, the benchmark GitHub workflow is using the {{spark-submit}} approach.

This propose to set {{IS_TESTING}} to true in {{BenchmarkBase}} so that it is always on.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org