Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16785
I don't find a way to improve `getAliasedConstraints` significantly by
re-writing its logic. The current way to improve its performance is using
parallel collection to do the transformation in parallel. It can cut the
running time by half (see benchmark in the pr description), but the running
time (13.5 secs) is still too long compared with 1.6.
We may consider #16775 which is an another solution to fix this issue by
checkpointing datasets for pipelines of long stages, or both of them.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
