[7.x][ML] Gain upper bound estimation for classification and regression #1568
Merged
valeriy42 merged 4 commits intoelastic:7.xfrom Nov 12, 2020
Merged
[7.x][ML] Gain upper bound estimation for classification and regression #1568valeriy42 merged 4 commits intoelastic:7.xfrom
valeriy42 merged 4 commits intoelastic:7.xfrom
Conversation
…lastic#1537) In this PR we start computing an upper bound on the potential gain from splitting a node. If the upper bound of the gain is lower than the currently smallest gain among all candidates, we ignore the node and this way prevent computations that are especially expensive on the large datasets. Since we avoid computation of the splits that we wouldn't be added to the tree anyway, this PR does not change the qualitative results. At the moment, we can only compute the upper bound for regression and binary classification. For multiclass classification we proceed as before. Note: this PR contains additional instrumentation to assess the performance improvement. I will remove this instrumentation in a follow-up PR after tests.
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.
In this PR we start computing an upper bound on the potential gain from splitting a node. If the upper bound of the gain is lower than the currently smallest gain among all candidates, we ignore the node and this way prevent computations that are especially expensive on the large datasets.
Since we avoid computation of the splits that we wouldn't be added to the tree anyway, this PR does not change the qualitative results.
At the moment, we can only compute the upper bound for regression and binary classification. For multiclass classification we proceed as before.
Note: this PR contains additional instrumentation to assess the performance improvement. I will remove this instrumentation in a follow-up PR after tests.
Backport of #1537