fix num_cpus flag #150
Merged
fix num_cpus flag #150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jpata
added a commit
that referenced
this pull request
Sep 15, 2023
* fix the num_cpus flag to actually change the number of cpus * fix eval, clic postprocessing
jpata
added a commit
that referenced
this pull request
Sep 15, 2023
* fix the num_cpus flag to actually change the number of cpus * fix eval, clic postprocessing Former-commit-id: cf35d66
jpata
added a commit
that referenced
this pull request
Sep 15, 2023
* fix the num_cpus flag to actually change the number of cpus * fix eval, clic postprocessing Former-commit-id: cf35d66
jpata
added a commit
that referenced
this pull request
Sep 25, 2023
* fix the num_cpus flag to actually change the number of cpus * fix eval, clic postprocessing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix the num_cpus flag to actually tell tensorflow to use a fixed number of threads. Useful to limit the application to a fixed CPU budget on a HPC.
In the previous version, using MirroredStrategy on CPU just blows up the RAM by a factor of Nthreads, which does not seem correct.