Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/19082
I agree with you. #18810 compares the following two code.
1. Interpreter execution of Java code by whole-stage codegen with passing
row data in scalar values
2. JITted execution of Java code by expression codegen with passing row
data using iterator
In the above case, 1. is slower than 2. due to the advantage of JIT
compilation.
#18931 can cut the boundary of whole-stage operators. *Hopefully*, this
cutting makes the byte code size smaller. #19082 can encourage this assumption.
Do you want add a feature to disable whole-stage codegen if JVM bytecode
size of one of cut methods is larger than 8KB after applying cutting at the
boundary of whole-stage operators?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
