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.

Sign up for GitHub

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

Jump to bottom

Add FAQ entry to discuss executor task concurrency configuration [skip ci] #4692

Merged
merged 2 commits into from
Feb 8, 2022
Merged

Add FAQ entry to discuss executor task concurrency configuration [skip ci] #4692

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
26972b2
Add FAQ entry to discuss executor task concurrency configuration
jlowe Feb 4, 2022
0cd2243
Update docs/FAQ.md
jlowe Feb 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -336,6 +336,20 @@ the I/O and starting the initial processing can suffer. But if you have a lot o
cannot be done on the GPU, like complex UDFs, the more tasks you have the more CPU processing you
can throw at it.

### How are `spark.executor.cores`, `spark.task.resource.gpu.amount`, and `spark.rapids.sql.concurrentGpuTasks` related?

The `spark.executor.cores` and `spark.task.resource.gpu.amount` configuration settings are inputs
to the Spark task scheduler and control the maximum number of tasks that can be run concurrently
on an executor, regardless of whether they are running CPU or GPU code at any point in time. See
the [Number of Tasks per Executor](tuning-guide.md#number-of-tasks-per-executor) section in the
tuning guide for more details.

The `spark.rapids.sql.concurrentGpuTasks` configuration setting is specific to the RAPIDS
Accelerator and further limits the number of concurrent tasks that are _actively_ running code on
the GPU or using GPU memory at any point in time. See the
[Number of Concurrent Tasks per GPU](tuning-guide.md#number-of-concurrent-tasks-per-gpu) section
of the tuning guide for more details.

### Why are multiple GPUs per executor not supported?

The RAPIDS Accelerator only supports a single GPU per executor because that was a limitation of
Expand Down