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
@pcmoritz mentioned that num_cpus=n is a ray.remote argument which is a convenient short hand for resources={"CPU": n}, and whenever we expect a resource dict, the only way to really specify it is via {"CPU": n}.
We should better document this:
having a section in the docs on what exactly a resource dict is and how it relates to num_cpu
link to this section from wherever we expect resource dicts.
Link
No response
The text was updated successfully, but these errors were encountered:
scottsun94
added
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
docs
An issue or change related to documentation
core
Issues that should be addressed in Ray Core
labels
Nov 12, 2024
rynewang
added
P2
Important issue, but not time-critical
and removed
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Nov 12, 2024
Description
@pcmoritz mentioned that
num_cpus=n
is aray.remote
argument which is a convenient short hand forresources={"CPU": n}
, and whenever we expect a resource dict, the only way to really specify it is via{"CPU": n}
.We should better document this:
num_cpu
Link
No response
The text was updated successfully, but these errors were encountered: