Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-35315

Keep benchmark result consistent between spark-submit and SBT

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.2.0
    • Fix Version/s: 3.2.0
    • Component/s: Tests
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              csun Chao Sun
              Reporter:
              csun Chao Sun
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: