Pass on nthreads to xgboost functions in scDblFinder#140
Merged
Conversation
Owner
|
Hi, |
Owner
|
Looks like this also changed with xgboost>3, and might even depend on how the package was compiled... but as I see no downside to your edits will just merge, so you can forget my question... |
Contributor
Author
|
I saw this on Linux, with |
Owner
|
if things look okay on the devel builds I'll port to release after |
Contributor
Author
|
Thank you! |
This file contains hidden or 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
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.
We recently had some cases where
scDblFinder()would grab all the cores on the machine, and run very slowly. Passing thenthreadsparameter to thexgboostfunctions (which I believe would otherwise resort toparallel::detectCores()) seems to improve the situation and it finishes quickly (although as far as I can see it still uses a bit more CPU than specified viaBPPARAM). The code below was enough to trigger the issue (both with versions 1.24.10 and 1.25.4):Is this something that you have also run into?
cc @mbstadler