-
- Downloads
[SPARK-15107][SQL] Allow varying # iterations by test case in Benchmark
## What changes were proposed in this pull request? This patch changes our micro-benchmark util to allow setting different iteration numbers for different test cases. For some of our benchmarks, turning off whole-stage codegen can make the runtime 20X slower, making it very difficult to run a large number of times without substantially shortening the input cardinality. With this change, I set the default num iterations to 2 for whole stage codegen off, and 5 for whole stage codegen on. I also updated some results. ## How was this patch tested? N/A - this is a test util. Author: Reynold Xin <rxin@databricks.com> Closes #12884 from rxin/SPARK-15107.
Showing
- core/src/main/scala/org/apache/spark/util/Benchmark.scala 10 additions, 11 deletionscore/src/main/scala/org/apache/spark/util/Benchmark.scala
- core/src/test/scala/org/apache/spark/util/collection/unsafe/sort/RadixSortSuite.scala 1 addition, 1 deletion...he/spark/util/collection/unsafe/sort/RadixSortSuite.scala
- sql/core/src/test/scala/org/apache/spark/sql/execution/BenchmarkWholeStageCodegen.scala 82 additions, 55 deletions...ache/spark/sql/execution/BenchmarkWholeStageCodegen.scala
Please register or sign in to comment