Skip to content
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

[FEA] Qualification tool triggers the AutoTuner module #739

Merged
merged 3 commits into from
Jan 25, 2024

Conversation

amahussein
Copy link
Collaborator

Signed-off-by: Ahmed Hussein (amahussein) a@ahussein.me

Fixes #700

This is an incremental step toward the full automation of App migration to GPU.

  • Add Qual arg --auto-tuner to toggle the AutoTuner module. Default is Off.
  • Add Qual arg --worker-info to pass the GPU worker info to the Qual's AutoTuner.
  • When AutoTuner is enabled, the Qual tool will launch the AutoTuner module to make some basic recommendations/comments based on the Spark/Env properties.
  • A new folder rapids_4_spark_qualification_output/tuning is created which contains a text formatted file for each app. Each file is named after the AppID.
  • No unit-tests is added for now because: 1- the recommendations are based on the Profiler's implementation; and the feature is disabled by default.
  • There will be followup to incrementally split the logic of the AutoTuner into two classes that aim to tailor the rules/policies of the recommendations to the CPU applications.

Signed-off-by: Ahmed Hussein (amahussein) <a@ahussein.me>

Fixes NVIDIA#700

This is an incremental step toward the full automation of App migration to GPU.

- Add Qual arg `--auto-tuner` to toggle the AutoTuner module. Default is Off.
- Add Qual arg `--worker-info` to pass the GPU worker info to the Qual's AutoTuner.
- When AutoTuner is enabled, the Qual tool will launch the AutoTuner module to make some basic recommendations/comments based on the Spark/Env properties.
- A new folder `rapids_4_spark_qualification_output/tuning` is created which contains a text formatted file for each app. Each file is named after the AppID.
- No unit-tests is added for now because: 1- the recommendations are based on the Profiler's implementation; and the feature is disabled by default.
- There will be followup to incrementally split the logic of the AutoTuner into two classes that aim to tailor the rules/policies of the recommendations to the CPU applications.
@amahussein amahussein added feature request New feature or request core_tools Scope the core module (scala) labels Jan 24, 2024
@amahussein amahussein self-assigned this Jan 24, 2024
@parthosa parthosa changed the title [FEA] Qualification tool triggers the AtutoTuner module [FEA] Qualification tool triggers the AutoTuner module Jan 24, 2024
Signed-off-by: Ahmed Hussein (amahussein) <a@ahussein.me>
Signed-off-by: Ahmed Hussein (amahussein) <a@ahussein.me>
@amahussein amahussein merged commit a154c0b into NVIDIA:dev Jan 25, 2024
13 checks passed
@amahussein amahussein deleted the spark-rapids-tools-700 branch January 25, 2024 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core_tools Scope the core module (scala) feature request New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEA] Refactor AutoTuner to work on CPU and GPU profiles
3 participants