Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21822
@rxin, I think this PR could possibly cause some performance effect given
the latest test ran above
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/93470/ and
from a rough scan of other builds:
```
ArithmeticExpressionSuite:
- SPARK-22499: Least and greatest should not generate codes beyond 64KB (11
minutes, 51 seconds)
CastSuite:
- cast string to timestamp (8 minutes, 42 seconds)
TPCDSQuerySuite:
- q14a-v2.7 (2 minutes, 29 seconds)
SQLQueryTestSuite:
- subquery/in-subquery/in-joins.sql (2 minutes, 36 seconds)
ContinuousStressSuite:
- only one epoch (3 minutes, 21 seconds)
- automatic epoch advancement (3 minutes, 21 seconds)
```
vs
https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-sbt-hadoop-2.7/4699/consoleFull
```
ArithmeticExpressionSuite:
- SPARK-22499: Least and greatest should not generate codes beyond 64KB (7
minutes, 49 seconds)
CastSuite:
- cast string to timestamp (1 minute)
TPCDSQuerySuite:
- q14a-v2.7 (3 seconds, 442 milliseconds)
SQLQueryTestSuite:
- subquery/in-subquery/in-joins.sql (2 minutes, 21 seconds)
ContinuousStressSuite:
- only one epoch (3 minutes, 21 seconds)
- automatic epoch advancement (3 minutes, 21 seconds)
```
There could of course other factors like machine's status as well but I
thought it's good to note while I am taking a look for those.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
