-
Notifications
You must be signed in to change notification settings - Fork 30
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
[Doc] add performance tuning page #494
Conversation
Signed-off-by: Bobby Wang <wbo4958@gmail.com>
docs/site/performance.md
Outdated
|
||
However, if you are using a spark-rapids-ml version earlier than 23.10.0 or a Spark | ||
standalone cluster version below 3.4.0, you still need to set | ||
`"spark.task.resource.gpu.amount"` equal to `"spark.executor.resource.gpu.amount"`. For example, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do they have to be equal? We just need to make sure there is one task per gpu not necessarily one task per executor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, You're right. New commit has fixed this part.
docs/site/performance.md
Outdated
... | ||
``` | ||
|
||
The above submit command specifies a request for 1 GPU and 12 CPUs per executor. So you can see, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
submit -> spark-submit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
docs/site/performance.md
Outdated
``` | ||
|
||
The above submit command specifies a request for 1 GPU and 12 CPUs per executor. So you can see, | ||
a total of 12 tasks per executor will be executed concurrently during the ETL phase. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add that stage level scheduling is then used internal to the library to automatically carry out the ML training phases using the required 1 gpu per task.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@wbo4958 Can this be merged to 23.10 also? |
* [Doc] add performance tuning page Signed-off-by: Bobby Wang <wbo4958@gmail.com> * comments --------- Signed-off-by: Bobby Wang <wbo4958@gmail.com>
No description provided.