-
Notifications
You must be signed in to change notification settings - Fork 37
FastLDF vs Original But Optimised LDF #1118
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
Draft
penelopeysm
wants to merge
25
commits into
main
Choose a base branch
from
py/fastldf2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+554
−112
Conversation
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
This reverts commit 93daa2b.
Contributor
Benchmark Report for Commit c44bae1Computer InformationBenchmark Results |
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.
This PR combines the changes from #1113 and #1115. I don't expect this should be merged, but I think it's worth having somewhere to compare the two.
It appears to me that FastLDF is still faster by about 3x, although allocations are equivalent now (at least for evals; grads are quite different). I am actually quite unsure where this comes from because when @mhauru and I were talking about this over Zoom, we thought that we had reduced the perf difference to around 1.5x or so. (Perhaps I'm just confused.) I'd be very happy if someone could try to reproduce this, the code is all below.
Benchmarks are run on 1.11.7, with 1 thread, as before. Qualitatively I observe the same on 1.12.1.
Interestingly, the one model where the two approaches are almost equivalent time-wise is
badvarnames. I wonder if that suggests that it's actually the NamedTuple optimisation doing a lot of the hard work here? I am too lazy to turn that optimisation off and rerun, but just throwing it out there, I guess.