Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/13504
@rxin, I don't have the specific performance numbers handy but in an
optimizer stress-test benchmark run by @ericl, these hashCode calls accounted
for roughly 40% of the total CPU time and this bottleneck was completely
eliminated by the caching added by this patch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]