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

Jump to bottom

add RhpcBLASctl to faq #170

Merged
merged 1 commit into from
Sep 5, 2024
Merged

add RhpcBLASctl to faq #170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 3 additions & 0 deletions mlr-org/faq.qmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,9 @@ When resampling or tuning a fast-fitting learner, it helps to chunk multiple res
The option [`mlr3.exec_chunk_bins`](https://mlr3.mlr-org.com/reference/mlr3-package.html#package-options) determines the number of chunks to split the resampling iterations into.
For example, when running a benchmark with 100 resampling iterations, `options("mlr3.exec_chunk_bins" = 4)` creates 4 computational jobs with 25 resampling iterations each.
This reduces the parallelization overhead and speeds up the execution.
The parallelization of the BLAS library can interfere with future parallelization due to over-utilization of the available cores.
Install [`RhpcBLASctl`](https://cran.r-project.org/web/packages/RhpcBLASctl/index.html) so that mlr3 can turn off the parallelization of BLAS.
`RhpcBLASctl` can only be included as an optional dependency due to licensing issues.

## Why is the parallelization of tuning slow? {#tuning-slow}

Expand Down
Loading