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

update about default cpus #300

Merged
merged 2 commits into from
Jun 24, 2022
Merged

update about default cpus #300

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a036a1b
update about default cpus
Jun 24, 2022
242f2d9
Update changelog/2022-06-24.md
Jun 24, 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 changelog/2022-06-24.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
## :warning: June 24, 2022

**CLI version: 0.8.65 **

This release includes an important update to how CPU and memory are allocated to experiments.

Prior to this release, Grid would set the default number of CPUs to 1 when creating runs and not explictly specifying `--cpus`.

We recently discovered an issue with runs where setting `--cpus` 1 would also reduce the memory, causing lots of OOM issues.
essiequoi marked this conversation as resolved.
Show resolved Hide resolved

So we've updated this behavior to set `--cpus` to 0 by default. This applies when creating runs with GPUs as well. By setting `--cpus` to 0, the backend will allocate all available CPU and memory to the experiment.


---