spark-instrumented-optimizer/core/benchmarks/KryoBenchmark-results.txt
HyukjinKwon ebf01ec3c1 [SPARK-34950][TESTS] Update benchmark results to the ones created by GitHub Actions machines
### What changes were proposed in this pull request?

https://github.com/apache/spark/pull/32015 added a way to run benchmarks much more easily in the same GitHub Actions build. This PR updates the benchmark results by using the way.

**NOTE** that looks like GitHub Actions use four types of CPU given my observations:

- Intel(R) Xeon(R) Platinum 8171M CPU  2.60GHz
- Intel(R) Xeon(R) CPU E5-2673 v4  2.30GHz
- Intel(R) Xeon(R) CPU E5-2673 v3  2.40GHz
- Intel(R) Xeon(R) Platinum 8272CL CPU  2.60GHz

Given my quick research, seems like they perform roughly similarly:

![Screen Shot 2021-04-03 at 9 31 23 PM](https://user-images.githubusercontent.com/6477701/113478478-f4b57b80-94c3-11eb-9047-f81ca8c59672.png)

I couldn't find enough information about Intel(R) Xeon(R) Platinum 8272CL CPU  2.60GHz but the performance seems roughly similar given the numbers.

So shouldn't be a big deal especially given that this way is much easier, encourages contributors to run more and guarantee the same number of cores and same memory with the same softwares.

### Why are the changes needed?

To have a base line of the benchmarks accordingly.

### Does this PR introduce _any_ user-facing change?

No, dev-only.

### How was this patch tested?

It was generated from:

- [Run benchmarks: * (JDK 11)](https://github.com/HyukjinKwon/spark/actions/runs/713575465)
- [Run benchmarks: * (JDK 8)](https://github.com/HyukjinKwon/spark/actions/runs/713154337)

Closes #32044 from HyukjinKwon/SPARK-34950.

Authored-by: HyukjinKwon <gurwls223@apache.org>
Signed-off-by: Max Gekk <max.gekk@gmail.com>
2021-04-03 23:02:56 +03:00

29 lines
2.8 KiB
Plaintext

================================================================================================
Benchmark Kryo Unsafe vs safe Serialization
================================================================================================
OpenJDK 64-Bit Server VM 1.8.0_282-b08 on Linux 5.4.0-1043-azure
Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
Benchmark Kryo Unsafe vs safe Serialization: Best Time(ms) Avg Time(ms) Stdev(ms) Rate(M/s) Per Row(ns) Relative
---------------------------------------------------------------------------------------------------------------------------
basicTypes: Int with unsafe:true 286 295 6 3.5 285.6 1.0X
basicTypes: Long with unsafe:true 320 327 5 3.1 319.8 0.9X
basicTypes: Float with unsafe:true 314 318 2 3.2 313.5 0.9X
basicTypes: Double with unsafe:true 310 319 6 3.2 309.9 0.9X
Array: Int with unsafe:true 5 6 1 217.9 4.6 62.2X
Array: Long with unsafe:true 8 9 1 121.5 8.2 34.7X
Array: Float with unsafe:true 5 6 0 217.5 4.6 62.1X
Array: Double with unsafe:true 9 9 1 117.3 8.5 33.5X
Map of string->Double with unsafe:true 51 52 1 19.7 50.9 5.6X
basicTypes: Int with unsafe:false 373 384 12 2.7 373.3 0.8X
basicTypes: Long with unsafe:false 373 391 9 2.7 372.6 0.8X
basicTypes: Float with unsafe:false 349 362 11 2.9 349.2 0.8X
basicTypes: Double with unsafe:false 358 372 10 2.8 358.0 0.8X
Array: Int with unsafe:false 25 29 1 40.0 25.0 11.4X
Array: Long with unsafe:false 35 39 1 28.2 35.5 8.1X
Array: Float with unsafe:false 10 12 1 100.2 10.0 28.6X
Array: Double with unsafe:false 17 20 1 58.3 17.1 16.7X
Map of string->Double with unsafe:false 48 53 2 20.6 48.5 5.9X