You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This is the follow on of issue - #580. Once we have support for driver log in Profiler tool, we should extend it to read both driver log and eventlogs and output the stats for unsupported operators. This could help in understanding why a certain query might be slow and also helps in prioritizing to add GPU support for unsupported operators.
For example: In a query if there are 2 unsupported operators, and when we look at the eventlogs one operator produces 100 rows(aggregate) and the other operator produces 10^9 rows(aggregate), the output should contain the aggregated number of rows for all the unsupported operators.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is the follow on of issue - #580. Once we have support for driver log in Profiler tool, we should extend it to read both driver log and eventlogs and output the stats for unsupported operators. This could help in understanding why a certain query might be slow and also helps in prioritizing to add GPU support for unsupported operators.
For example: In a query if there are 2 unsupported operators, and when we look at the eventlogs one operator produces 100 rows(aggregate) and the other operator produces 10^9 rows(aggregate), the output should contain the aggregated number of rows for all the unsupported operators.
The text was updated successfully, but these errors were encountered: