Output Details

The qualification tool will generate a number of detailed reports in addition to the high-level recommendations. The summary report goes to STDOUT and by default it outputs log/CSV files under ./rapids_4_spark_qualification_output/ that contain the processed applications. The output will go into your default filesystem and it supports both local filesystem and HDFS. Note that if you are on an HDFS cluster the default filesystem is likely HDFS for both the input and output. If you want to point to the local filesystem be sure to include prefix file: in the path.

The qualification tool generates a brief summary on the STDOUT, which also gets saved as a text file. The detailed report of the processed apps is saved as a set of CSV files that can be used for post-processing. The CSV reports include the estimated performance if the app is run on the GPU for each of the following: app execution; stages; and execs.

Starting with release “22.06”, the default is to generate the report into two different formats: text files; and HTML.

The tree structure of the output directory ${OUTPUT_FOLDER}/rapids_4_spark_qualification_output is as follows:

Tree structure of the output directory rapids_4_spark_qualification_output

            

            
    rapids_4_spark_qualification_output
    ├── rapids_4_spark_qualification_output.csv
    ├── rapids_4_spark_qualification_output.log
    ├── rapids_4_spark_qualification_output_persql.log
    ├── rapids_4_spark_qualification_output_persql.csv
    ├── rapids_4_spark_qualification_output_execs.csv
    ├── rapids_4_spark_qualification_output_stages.csv
    ├── rapids_4_spark_qualification_output_mlfunctions.csv
    ├── rapids_4_spark_qualification_output_mlfunctions_totalduration.csv
    ├── rapids_4_spark_qualification_output_unsupportedOperators.csv
    ├── rapids_4_spark_qualification_output_unsupportedOperatorsStageDuration.csv
    ├── runtime.properties
    ├── tuning
    │   ├── app-001-0001.conf
    │   └── app-001-0001.log
    └── ui
        ├── assets
        │   ├── bootstrap/
        │   ├── datatables/
        │   ├── jquery/
        │   ├── mustache-js/
        │   └── spur/
        ├── css
        │   └── rapids-dashboard.css
        ├── html
        │   ├── application.html
        │   ├── index.html
        │   ├── raw.html
        │   └── sql-recommendation.html
        └── js
            ├── app-report.js
            ├── data-output.js
            ├── per-sql-report.js
            ├── qual-report.js
            ├── raw-report.js
            ├── ui-config.js
            └── uiutils.js
        

For information on the files content and processing the Qualification report and the recommendation, please refer to Understanding the Qualification tool output and Output Formats sections below.

When the “--auto-tuner” argument is enabled, one notable addition is the creation of a new subdirectory within the output folder named “tuning”. Within this directory, each application will have two files:

• <appi-id>.log: This file contains the recommendations and accompanying comments.

• <app-id>.conf: Here, you’ll find the combined Spark properties.

It’s worth noting that certain properties with sensitive information will be redacted in the combined results.

The Auto-Tuner output has 2 main sections:

1. Spark Properties: A list of Apache Spark configurations to tune the performance of the app. The list is the result of diff between the existing app configurations and the recommended ones. Therefore, a recommendation matches the existing app configuration, it will not show up in the list.

2. Comments: A list of messages to highlight properties that were missing in the app configurations, or the cause of failure to generate the recommendations.

Examples

Example of a successful run with missing softwareProperties

            

            
Spark Properties:

–conf spark.executor.cores=16
–conf spark.executor.instances=8
–conf spark.executor.memory=32768m
–conf spark.executor.memoryOverhead=7372m
–conf spark.rapids.memory.pinnedPool.size=4096m
–conf spark.rapids.sql.concurrentGpuTasks=2
–conf spark.sql.files.maxPartitionBytes=512m
–conf spark.sql.shuffle.partitions=200
–conf spark.task.resource.gpu.amount=0.0625

Comments:

-  ‘spark.executor.instances’ was not set.
-  ‘spark.executor.cores’ was not set.
-  ‘spark.task.resource.gpu.amount’ was not set.
-  ‘spark.rapids.sql.concurrentGpuTasks’ was not set.
-  ‘spark.executor.memory’ was not set.
-  ‘spark.rapids.memory.pinnedPool.size’ was not set.
-  ‘spark.executor.memoryOverhead’ was not set.
-  ‘spark.sql.files.maxPartitionBytes’ was not set.
-  ‘spark.sql.shuffle.partitions’ was not set.
-  ‘spark.sql.adaptive.enabled’ should be enabled for better
    performance.
        

Example of a successful run with missing softwareProperties. Only two recommendations did not match the existing app configurations.

            

            
Spark Properties:

--conf spark.executor.instances=8
--conf spark.sql.shuffle.partitions=200

Comments:

- 'spark.sql.shuffle.partitions' was not set.
        

Example showing the output when loading the worker info has failed.

            

            
Cannot recommend properties. See Comments.

Comments:
- java.io.FileNotFoundException: File worker-info.yaml does not exist
- 'spark.executor.memory' should be set to at least 2GB/core.
- 'spark.executor.instances' should be set to (gpuCount * numWorkers).
- 'spark.task.resource.gpu.amount' should be set to Max(1, (numCores / gpuCount)).
- 'spark.rapids.sql.concurrentGpuTasks' should be set to Max(4, (gpuMemory / 8G)).
- 'spark.rapids.memory.pinnedPool.size' should be set to 2048m.
- 'spark.sql.adaptive.enabled' should be enabled for better performance.
        

For each processed Spark application, the Qualification tool generates two main fields to help quantify the expected acceleration of migrating a Spark application or query to GPU.

1. Estimated GPU Duration: predicted runtime of the app if it was run on GPU. It is the sum of the accelerated operator durations and ML functions duration(if applicable) along with durations that could not run on GPU because they are unsupported operators or not SQL/Dataframe.

2. Estimated Speed-up: the estimated speed-up is simply the original CPU duration of the app divided by the estimated GPU duration. That will estimate how much faster the application would run on GPU.

The lower the estimated GPU duration, the higher the “Estimated Speed-up”. The processed applications or queries are ranked by the “Estimated Speed-up”. Based on how high the estimated speed-up, the tool classifies the applications into the following different categories:

• Strongly Recommended

• Recommended

• Not Recommended

• Not Applicable: indicates that the app has job or stage failures.

As mentioned before, the tool does not guarantee the applications or queries with the highest recommendation will actually be accelerated the most. Please refer to Supported operators guide.

In addition to the recommendation, the Qualification tool reports a set of metrics in tasks of SQL Dataframe operations within the scope of: “Entire App”; “Stages”; and “Execs”. The report is divided into three main levels. The fields of each level are described in details in the following sections: Detailed App Report, Stages report, and Execs report. Then we describe the output formats and their file locations in Output Formats section.

There is an option to print a report at the SQL query level in addition to the application level.

Detailed App Report

The report represents the entire app execution, including unsupported operators and non-SQL operations.

1. App Name

2. App ID

3. Recommendation: recommendation based on Estimated Speed-up Factor, where an app can be “Strongly Recommended”, “Recommended”, “Not Recommended”, or “Not Applicable”. The latter indicates that the app has job or stage failures.

4. App Duration

5. SQL DF duration: wall-Clock time duration that includes only SQL-Dataframe queries.

6. GPU Opportunity: wall-Clock time that shows how much of the SQL duration and ML functions(if applicable) can be accelerated on the GPU.

7. Estimated GPU Duration

8. Estimated GPU Speedup

9. Estimated GPU Time Saved: estimated wall-Clock time saved if it was run on the GPU.

10. SQL Dataframe Task Duration: amount of time spent in tasks of SQL Dataframe operations.

11. Executor CPU Time Percent: this is an estimate at how much time the tasks spent doing processing on the CPU vs waiting on IO. This is not always a good indicator because sometimes the IO that is encrypted and the CPU has to do work to decrypt it, so the environment you are running on needs to be taken into account.

12. SQL Ids with Failures: SQL Ids of queries with failed jobs.

13. Unsupported Read File Formats and Types: looks at the Read Schema and reports the file formats along with types which may not be fully supported. Example: JDBC[*]. Note that this is based on the current version of the plugin and future versions may add support for more file formats and types.

14. Unsupported Write Data Format: reports the data format which we currently don’t support, i.e. if the result is written in JSON or CSV format.

15. Complex Types: looks at the Read Schema and reports if there are any complex types(array, struct or maps) in the schema.

16. Nested Complex Types: nested complex types are complex types which contain other complex types (Example: array<struct<string,string>>). Note that it can read all the schemas for DataSource V1. The Data Source V2 truncates the schema, so if you see “...”, then the full schema is not available. For such schemas we read until ... and report if there are any complex types and nested complex types in that.

17. Potential Problems: some UDFs and nested complex types. Please keep in mind that the tool is only able to detect certain issues.

18. Longest SQL Duration: the maximum amount of time spent in a single task of SQL Dataframe operations.

19. NONSQL Task Duration Plus Overhead: Time duration that does not span any running SQL task.

20. Unsupported Task Duration: sum of task durations for any unsupported operators.

21. Supported SQL DF Task Duration: sum of task durations that are supported by RAPIDS GPU acceleration.

22. Task Speedup Factor: the average speed-up of all stages.

23. App Duration Estimated: True or False indicates if we had to estimate the application duration. If we had to estimate it, the value will be True and it means the event log was missing the application finished event, so we will use the last job or sql execution time we find as the end time used to calculate the duration.

24. Unsupported Execs: reports all the execs that are not supported by GPU in this application. Note that an Exec name may be printed in this column if any of the expressions within this Exec is not supported by GPU. If the resultant string exceeds maximum limit (25), then … is suffixed to the STDOUT and full output can be found in the CSV file.

25. Unsupported Expressions: reports all expressions not supported by GPU in this application.

26. Read Schema: shows the datatypes and read formats. This field is only listed when the argument --report-read-schema is passed to the CLI.

27. Estimated Frequency: application executions per month assuming uniform distribution, default frequency is daily (30 times per month) and minimum frequency is monthly (1 time per month). For a given log set, determines a logging window using the earliest start time and last end time of all logged applications. Counts the number of executions of a specific App Name over the logging window and converts the frequency to per month (30 days). Applications that are only ran once are assigned the default frequency.

By default, the applications and queries are sorted in descending order by the following fields:

• Recommendation

• Estimated GPU Speedup

• Estimated GPU Time Saved

• End Time

Stages Report

For each stage used in SQL operations, the Qualification tool generates the following information:

1. App ID

2. Stage ID

3. Average Speedup Factor: the average estimated speed-up of all the operators in the given stage.

4. Stage Task Duration: amount of time spent in tasks of SQL Dataframe operations for the given stage.

5. Unsupported Task Duration: sum of task durations for the unsupported operators. For more details, see the Supported operators guide.

6. Stage Estimated: True or False indicates if we had to estimate the stage duration.

Execs Report

The Qualification tool generates a report of the “Exec” in the “SparkPlan” or “Executor Nodes” along with the estimated acceleration on the GPU. Please refer to the Supported operators guide for more details on limitations on UDFs and unsupported operators.

1. App ID

2. SQL ID

3. Exec Name: example Filter, HashAggregate

4. Expression Name

5. Task Speedup Factor: it is simply the average acceleration of the operators based on the original CPU duration of the operator divided by the GPU duration. The tool uses historical queries and benchmarks to estimate a speed-up at an individual operator level to calculate how much a specific operator would accelerate on GPU.

6. Exec Duration: wall-Clock time measured since the operator starts till it is completed.

7. SQL Node Id

8. Exec Is Supported: whether the Exec is supported by RAPIDS or not. Please refer to the Supported operators guide.

9. Exec Stages: an array of stage IDs

10. Exec Children

11. Exec Children Node Ids

12. Exec Should Remove: whether the Op is removed from the migrated plan.

Parsing Expressions within each Exec

The Qualification tool looks at the expressions in each Exec to provide a fine-grained assessment of RAPIDS’ support.

Note that it is not possible to extract the expressions for each available Exec: - some Execs do not take any expressions, and - some execs may not show the expressions in the eventlog.

The following table lists the exec’s name and the status of parsing their expressions where: - “Expressions Unavailable” marks the Execs that do not show expressions in the eventlog - “Fully Parsed” marks the Execs that have their expressions fully parsed by the Qualification tool - “In Progress” marks the Execs that are still being investigated; therefore, a set of the marked Execs may be fully parsed in future releases.

MLFunctions Report

The Qualification tool generates a report if there are SparkML or Spark XGBoost functions used in the eventlog. The functions in “spark.ml.” or “spark.XGBoost.” packages are displayed in the report.

1. App ID

2. Stage ID

3. ML Functions: List of ML functions used in the corresponding stage.

4. Stage Task Duration: amount of time spent in tasks containing ML functions for the given stage.

MLFunctions Total Duration Report

The Qualification tool generates a report of total duration across all

1. App ID

2. _Stage_Ids : Stage Id’s corresponding to the given ML function.

3. ML Function Name: ML function name supported on GPU.

4. Total Duration: total duration across all stages for the corresponding ML function.

The Qualification tool generates the output as CSV/log files. Starting from “22.06”, the default is to generate the report into two different formats: CSV/log files; and HTML.

HTML Report

Starting with release “22.06”, the HTML report is generated by default under the output directory ${OUTPUT_FOLDER}/rapids_4_spark_qualification_output/ui. The HTML report is disabled by passing --no-html-report as described in the Qualification tool options section above. To browse the content of the html report:

1. For HDFS or remote node, copy the directory of ${OUTPUT_FOLDER}/rapids_4_spark_qualification_output/ui to your local node.

2. Open rapids_4_spark_qualification_output/ui/index.html in your local machine’s web-browser (Chrome/Firefox are recommended).

The HTML view renders the detailed information into tables that allow following features:

• searching

• ordering by specific column

• exporting table into CSV file

• interactive filter by recommendations and/or user-name.

By default, all tables show 20 entries per page, which can be changed by selecting a different page-size in the table’s navigation bar.

The following sections describe the HTML views.

Application Recommendations Summary

index.html shows the summary of the estimated GPU performance. The “GPU Recommendations Table” lists the processed applications ranked by the “Estimated GPU Speed-up” along with the ability to search, and filter the results. By clicking the “App ID” link of a specific app, you navigate to the details view of that app which is described in App-Details View section.

The summary report contains the following components:

1. Stats-Row: statistics card summarizing the following information:

   1. “Total Applications”: total number of applications analyzed by the Qualification tool and the total execution time.

   2. “RAPIDS Candidates”: marks the number applications that are either “Recommended”, or “Strongly Recommended”.

   3. “GPU Opportunity”: shows the total of “GPU Opportunity” and “SQL DF duration” fields across all the apps.

2. GPU Recommendations Table: this table lists all the analyzed applications along with subset of fields that are directly involved in calculating the GPU performance estimate. Each row expands showing more fields by clicking on the control column.

3. The searchPanes with the capability to search the app list by selecting rows in the panes. The “Recommendations” and “Spark User” filters are cascaded which allows the panes to be filtered based on the values selected in the other pane.

4. Text Search field that allows further filtering, removing data from the result set as keywords are entered. The search box will match on multiple columns including: “App ID”, “App Name”, “Recommendation”

5. HTML5 export button saves the table to CSV file into the browser’s default download folder.

6. The Raw Data link in the left navigation bar redirects to a detailed report.

7. The Per-SQL Data link in the left navigation bar redirects to a summary report that shows the per-SQL estimated GPU performance.

Qualification-HTML-Recommendation-View

App-Details View

When you click the “App ID” of a specific row in the “GPU Recommendations Table”, the browser navigates to this view which shows the metrics and estimated GPU performance for the given application. It contains the following main components:

1. Card title: contains the application name and the Recommendation.

2. Stats-Row: statistics card summarizing the following information:

   1. “App Duration”: the total execution time of the app, marking the start and end time.

   2. “GPU Opportunity”: the wall-Clock time that shows how much of the SQL duration can be accelerated on the GPU. It shows the actual wall-Clock time duration that includes only SQL-Dataframe queries including non-supported ops, dubbed “SQL DF Duration”. This is followed by “Task Speed-up Factor” which represents the average speed-up of all app stages.

   3. “Estimated GPU Duration”: the predicted runtime of the app if it was run on GPU. For convenience, it calculates the estimated wall-clock time difference between the CPU and GPU executions. The original CPU duration of the app divided by the estimated GPU duration and displayed as “App Speed-up”.

3. Application Details: this table lists all the fields described previously in the Detailed App report section. Note that this table has more columns than can fit in a normal browser window. Therefore, the UI application dynamically optimizes the layout of the table to fit the browser screen. By clicking on the control column, the row expands to show the remaining hidden columns.

   

4. Stage Details Table: lists all the app stages with set of columns listed in Stages report section. The HTML5 export button saves the table to CSV file into the browser’s default download folder.

   

   The table has cascaded searchPanes, which means that the table allows the panes to be filtered based on the values selected in the other panes.

   There are three searchPanes:

   1. “Is Stage Estimated”: it splits the stages into two groups based on whether the stage duration time was estimated or not.

   2. “Speed-up”: groups the stages by their “average speed-up”. Each stage can belong to one of the following predefined speed-up ranges: 1.0 (No Speed-up); [1.0, 1.3]; [1.3, 2.5]; [2.5, 5]; and [5, ]. The search-pane does not show a range bucket if its count is 0.

   3. “Tasks GPU Support”: this filter can be used to find stages having all their execs supported by the GPU.

5. Execs Details Table: lists all the app Execs with set of columns listed in Execs report section. The HTML5 export button saves the table to CSV file into the browser’s default download folder.

   

   The table has cascaded searchPanes, which means that the table allows the panes to be filtered based on the values selected in the other panes.

   There are three searchPanes:

   1. “Exec”: filters the rows by exec name. This filter also allows text searching by typing into the filter-title as a text input.

   2. “Speed-up”: groups the stages by their “average speed-up”. Each stage can belong to one of the following predefined speed-up ranges: 1.0 (No Speed-up); ]1.0, 1.3[; [1.3, 2.5[; [2.5, 5[; and [5, _]. The search-pane does not show a range bucket if its count is 0.

   3. “GPU Support”: filters the execs whether an exec is supported by GPU or not.

   4. “Stage ID”: filters rows by the stage ID. It also allows text-searching by typing into the filter-title as a text input.

   5. “Is Exec Removed”: filters rows that were removed from the migrated plan.

   6. SQL Details Table: lists Per-SQL GPU recommendation. The HTML5 export button saves the table to CSV file into the browser’s default download folder. The rows in the table can be filtered by “SQL Description”, “SQL ID”, or “Recommendation”.

Raw Data

raw.html displays all the fields listed in “Detailed App Report” in more readable format. Columns representing “time duration” are rounded to nearest “ms”, “seconds”, “minutes”, and “hours”. The search box will match on multiple columns including: “App ID”, “App Name”, “Recommendation”, “User Name”, “Unsupported Write Data Format”, “Complex Types”, “Nested Complex Types”, and “Read Schema”. The detailed table can also be exported as a CSV file into the browser’s default download folder.

Note that this table has more columns than can fit in a normal browser window. Therefore, the UI application dynamically optimizes the layout of the table to fit the browser screen. By clicking on the control column, the row expands to show the remaining hidden columns.

Per-SQL Data

sql-recommendation.html displays a summary of the estimate GPU performance for each query. Note that the SQL queries across all the apps are combined in a single view; therefore, the “SQL ID” field may not be unique.

Text and CSV files

The Qualification tool generates a set of log/CSV files in the output folder ${OUTPUT_FOLDER}/rapids_4_spark_qualification_output. The content of each file is summarized in the following two sections.

Application Report Summary

The Qualification tool generates a brief summary that includes the projected application’s performance if the application is run on the GPU. Beside sending the summary to STDOUT, the Qualification tool generates text as rapids_4_spark_qualification_output.log

The summary report outputs the following information: “App Name”, “App ID”, “App Duration”, “SQL DF duration”, “GPU Opportunity”, “Estimated GPU Duration”, “Estimated GPU Speed-up”, “Estimated GPU Time Saved”, and “Recommendation”.

Sample summary in text format. The duration(s) reported are in milliseconds.

            

            
+------------+--------------+----------+----------+-------------+-----------+-----------+-----------+--------------------+-------------------------------------------------------+
|  App Name  |    App ID    |    App   |  SQL DF  |     GPU     | Estimated | Estimated | Estimated |  Recommendation    |      Unsupported Execs        |Unsupported Expressions|
|            |              | Duration | Duration | Opportunity |    GPU    |    GPU    |    GPU    |                    |                               |                       |
|            |              |          |          |             |  Duration |  Speedup  |    Time   |                    |                               |                       |
|            |              |          |          |             |           |           |   Saved   |                    |                               |                       |
+============+==============+==========+==========+=============+===========+===========+===========+====================+=======================================================+
| appName-01 | app-ID-01-01 |    898429|    879422|       879422|  273911.92|       3.27|  624517.06|Strongly Recommended|                               |                       |
+------------+--------------+----------+----------+-------------+-----------+-----------+-----------+--------------------+-------------------------------------------------------+
| appName-02 | app-ID-02-01 |      9684|      1353|         1353|    8890.09|       1.08|      793.9|     Not Recommended|Filter;SerializeFromObject;S...|           hex         |
+------------+--------------+----------+----------+-------------+-----------+-----------+-----------+--------------------+-------------------------------------------------------+
        

In the above example, two application event logs were analyzed. “app-ID-01-01” is “Strongly Recommended” because Estimated GPU Speedup is ~3.27. On the other hand, the estimated acceleration running “app-ID-02-01” on the GPU is not high enough; hence the app is not recommended.

Per SQL Query Report Summary

The Qualification tool has an option to generate a report at the per SQL query level. It generates a brief summary that includes the projected queries performance if the query is run on the GPU. Beside sending the summary to STDOUT, the Qualification tool generates text as rapids_4_spark_qualification_output_persql.log

The summary report outputs the following information: “App Name”, “App ID”, “SQL ID”, “SQL Description”, “SQL DF duration”, “GPU Opportunity”, “Estimated GPU Duration”, “Estimated GPU Speed-up”, “Estimated GPU Time Saved”, and “Recommendation”.

Sample Per SQL output in text. The duration(s) reported are in milliseconds.

            

            
+------------+--------------+----------+---------------+----------+-------------+-----------+-----------+-----------+--------------------+
|  App Name  |    App ID    |  SQL ID  |      SQL      |  SQL DF  |     GPU     | Estimated | Estimated | Estimated |  Recommendation    |
|            |              |          |  Description  | Duration | Opportunity |    GPU    |    GPU    |    GPU    |                    |
|            |              |          |               |          |             |  Duration |  Speedup  |    Time   |                    |
|            |              |          |               |          |             |           |           |   Saved   |                    |
+============+==============+==========+===============+==========+=============+===========+===========+===========+====================+
| appName-01 | app-ID-01-01 |         1|        query41|       571|          571|     187.21|       3.05|     383.78|Strongly Recommended|
+------------+--------------+----------+---------------+----------+-------------+-----------+-----------+-----------+--------------------+
| appName-02 | app-ID-02-01 |         3|        query44|      1116|            0|    1115.98|        1.0|       0.01|     Not Recommended|
+------------+--------------+----------+---------------+----------+-------------+-----------+-----------+-----------+--------------------+
        

Detailed App Report

Entire App Report

The first part of the detailed report is saved as rapids_4_spark_qualification_output.csv. The apps are processed and ranked by the Estimated GPU Speed-up. In addition to the fields listed in the “Report Summary”, it shows all the app fields. The duration(s) are reported are in milliseconds.

Per SQL Report

The second file is saved as rapids_4_spark_qualification_output_persql.csv. This contains the per SQL query report in CSV format.

Sample output in text:

            

            
+---------------+-----------------------+------+----------------+---------------+---------------+----------------------+---------------------+------------------------+--------------------+
|       App Name|                 App ID|SQL ID| SQL Description|SQL DF Duration|GPU Opportunity|Estimated GPU Duration|Estimated GPU Speedup|Estimated GPU Time Saved|      Recommendation|
+===============+=======================+======+================+===============+===============+======================+=====================+========================+====================+
|NDS - Power Run|app-20220702220255-0008|   103|         query87|          15871|          15871|               4496.03|                 3.53|                11374.96|Strongly Recommended|
|NDS - Power Run|app-20220702220255-0008|   106|         query38|          11077|          11077|               3137.96|                 3.53|                 7939.03|Strongly Recommended|
+---------------+-----------------------+------+----------------+---------------+---------------+----------------------+---------------------+------------------------+--------------------+
        

Stages Report

The third file is saved as rapids_4_spark_qualification_output_stages.csv.

Sample output in text:

            

            
+--------------+----------+-----------------+------------+---------------+-----------+
|    App ID    | Stage ID | Average Speedup | Stage Task |  Unsupported  |   Stage   |
|              |          |      Factor     |  Duration  | Task Duration | Estimated |
+==============+==========+=================+============+===============+===========+
| app-ID-01-01 |       25 |             2.1 |         23 |             0 |     false |
+--------------+----------+-----------------+------------+---------------+-----------+
| app-ID-02-01 |       29 |            1.86 |          0 |             0 |      true |
+--------------+----------+-----------------+------------+---------------+-----------+
        

Execs Report

The last file is saved rapids_4_spark_qualification_output_execs.csv. Similar to the app and stage information, the table shows estimated GPU performance of the SQL Dataframe operations.

Sample output in text:

            

            
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+
|    App ID    | SQL ID |         Exec Name         |    Expression Name    | Task Speedup |   Exec   | SQL Node |  Exec Is  |  Exec  |        Exec Children       | Exec Children | Exec Should |
|              |        |                           |                       |    Factor    | Duration |    Id    | Supported | Stages |                            |    Node Ids   |    Remove   |
+==============+========+===========================+=======================+==============+==========+==========+===========+========+============================+===============+=============+
| app-ID-02-01 |      7 | Execute CreateViewCommand |                       |          1.0 |        0 |        0 |     false |        |                            |               |       false |
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+
| app-ID-02-01 |     24 |                   Project |                       |          2.0 |        0 |       21 |      true |        |                            |               |       false |
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+
| app-ID-02-01 |     24 |              Scan parquet |                       |          2.0 |      260 |       36 |      true |     24 |                            |               |       false |
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+
| app-ID-02-01 |     15 | Execute CreateViewCommand |                       |          1.0 |        0 |        0 |     false |        |                            |               |       false |
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+
| app-ID-02-01 |     24 |                   Project |                       |          2.0 |        0 |       14 |      true |        |                            |               |       false |
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+
| app-ID-02-01 |     24 |     WholeStageCodegen (6) | WholeStageCodegen (6) |          2.8 |      272 |        2 |      true |     30 | Project:BroadcastHashJoin: |         3:4:5 |       false |
|              |        |                           |                       |              |          |          |           |        |              HashAggregate |               |             |
+--------------+--------+---------------------------+-----------------------+--------------+----------+----------+-----------+--------+----------------------------+---------------+-------------+