-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Profiler ignoring some reused subqueries #718
Labels
Comments
#693 is an attempt at fixing this. |
I remember that I handled the "ReusedExchange" in the Qualification tool before 2e25ce9 |
amahussein
added a commit
to amahussein/spark-rapids-tools
that referenced
this issue
Jan 25, 2024
Signed-off-by: Ahmed Hussein (amahussein) <[email protected]> Fixes NVIDIA#718 - Reused subqueries should be excluded from the metrics. - Added a common graph builder to be used for both CPU/GPU logs - Added the unit test for GPU eventlogs
This was referenced Jan 25, 2024
amahussein
added a commit
that referenced
this issue
Jan 26, 2024
* Remove ReusedSubquery from SparkPlanGraph construction Fixes #718 - Reused subqueries should be excluded from the metrics. - Added a common graph builder to be used for both CPU/GPU logs - Added the unit test for GPU eventlogs --------- Signed-off-by: Ahmed Hussein (amahussein) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In the profiler when we construct a
SparkPlanGraph
object fromspakPlanInfo
, there are two problems:SubqueryBroadcast
can also be reused as a subquery.GpuSubquery
andGpuSubqueryBroadcast
as reusable.This results in reused subqueries counted in all the metrics, perhaps a source of qualification tool inaccuracy.
Steps/Code to reproduce bug
Profile any cpu query with a
ReusedSubquery
that is aSubqueryBroadcast
, the reused subquery is shown in the metrics. Any gpu query with reused subqueries also show up.Expected behavior
Reused subqueries should be excluded from the metrics.
The text was updated successfully, but these errors were encountered: