[SPARK-29320][TESTS] Compare sql/core
module in JDK8/11 (Part 1)
#25992
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR regenerates the following
sql/core
benchmarks in JDK8/11 to compare the result.(These are less time-consuming half of the all
sql/core
benchmarks)AggregateBenchmark
BloomFilterBenchmark
BuiltInDataSourceWriteBenchmark
CSVBenchmark
ColumnarBatchBenchmark
CompressionSchemeBenchmark
DataSourceReadBenchmark
DatasetBenchmark
DateTimeBenchmark
ExternalAppendOnlyUnsafeRowArrayBenchmark
ExtractBenchmark
FilterPushdownBenchmark
HashedRelationMetricsBenchmark
InExpressionBenchmark
JoinBenchmark
MakeDateTimeBenchmark
MiscBenchmark
OrcNestedSchemaPruningBenchmark
OrcV2NestedSchemaPruningBenchmark
ParquetNestedSchemaPruningBenchmark
PrimitiveArrayBenchmark
RangeBenchmark
SortBenchmark
UDFBenchmark
UnsafeArrayDataBenchmark
WideSchemaBenchmark
WideTableBenchmark
Why are the changes needed?
According to the result, there are some difference between JDK8/JDK11. For example,
ByteBuffer API
andDirectByteBuffer
performance is switched like the following.JDK8
JDK11
Does this PR introduce any user-facing change?
No.
How was this patch tested?
This is a test-only PR. We need to run benchmark.