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

["Yuming Wang (Jira)" <ji...@apache.org>]

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

Yuming Wang resolved SPARK-35315.
---------------------------------
    Fix Version/s: 3.2.0
       Resolution: Fixed

Issue resolved by pull request 32440
[https://github.com/apache/spark/pull/32440]

> 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
>            Assignee: Chao Sun
>            Priority: Minor
>             Fix For: 3.2.0
>
>
> 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