Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Limiting number of cpus used?
See original GitHub issueI’ve been noticing that when I run UMAP part of the computation runs in parallel. I’d like to be able to limit the number of processes that get used per transformation. This would be useful for keeping a decent cpu utilization rate without risking getting my jobs killed.
I’ve tried limiting the number of threads numba uses (numba.config.NUMBA_NUM_THREADS), but that hasn’t seemed to work.
Is this something which is currently configurable, or a feature that could be added?
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, that pull request got merged and the
n_jobsparameter now makes use of it, so it should work if you set it.@ivirshup Any updates?