reduce overhead of to_sparse_data_frame()
#1172
Merged
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.
Noticed this when reviewing #1167 but it's unrelated to that PR. If we do the "cheap" side of the
&&
first, we can cut down on the overhead of "not converting to sparse when we don't want to." :)Before this PR:
Now:
We're talking about 1.5% of the total time in
fit(lr, mpg ~ ., mtcars)
vs 2.5%, but seems like a simple enough change to be worth it!