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

Improve FairGBM multi-threading #21

Open
AndreFCruz opened this issue Jul 20, 2022 · 0 comments
Open

Improve FairGBM multi-threading #21

AndreFCruz opened this issue Jul 20, 2022 · 0 comments
Labels
discovery This is an exploratory task (high uncertainty) enhancement New feature or request low priority Nice to have but not crucial M effort T-shirt effort weighing: M
Projects
Open Source Release

Comments

@AndreFCruz
Copy link
Contributor

According to our perf and valgrind benchmarks, a large percentage of CPU time is spent on synchronization of separate threads during training.

The net outcome of multi-threading is still positive, however when using OMP_NUM_THREADS=4 our code will only consistently use 2 threads, seeming unable to fully parallelize.
@AndreFCruz AndreFCruz added enhancement New feature or request M effort T-shirt effort weighing: M discovery This is an exploratory task (high uncertainty) labels Jul 20, 2022
@AndreFCruz AndreFCruz added the low priority Nice to have but not crucial label Aug 9, 2022
@GoncaloArs GoncaloArs moved this from To do to Backlog/To be groomed in Open Source Release Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discovery This is an exploratory task (high uncertainty) enhancement New feature or request low priority Nice to have but not crucial M effort T-shirt effort weighing: M
Projects
Open Source Release
Backlog/To be groomed
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AndreFCruz