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.

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

XGBoost: default params when GPU is enabled #8475

Closed
exalate-issue-sync bot opened this issue May 12, 2023 · 2 comments
Closed

XGBoost: default params when GPU is enabled #8475

exalate-issue-sync bot opened this issue May 12, 2023 · 2 comments

Comments

@exalate-issue-sync
Copy link

From investigation of AutoML results between {{rel-yau-6}} and {{rel-yau-11}}, we notice a degradation of performance in XGBoost training.
See the discussion at [https://h2oai.slack.com/archives/C0E0ADTM1/p1576683431088900?thread_ts=1576604011.073300&cid=C0E0ADTM1|https://h2oai.slack.com/archives/C0E0ADTM1/p1576683431088900?thread_ts=1576604011.073300&cid=C0E0ADTM1]

Suggestions:

  • disable parallel training of CV models for XGBoost if GPU is enabled: method {{XGBoost#nModelsInParallel}}.
  • use {{updater= grow_gpu_hist}} on GPU.
@exalate-issue-sync
Copy link
Author

Jan Sterba commented: fixed, the rafactor to using tree_method for GPU had the side-effect of suing gpu_predictor withch probably made CV models slower

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Migration Info

Jira Issue: PUBDEV-7164
Assignee: Jan Sterba
Reporter: Sebastien Poirier
State: Resolved
Fix Version: 3.28.0.2
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#4186
#4257

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant