Draft a benchmark-file #8
Merged
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
Benchmarks everything from the possible features with naive julia implementations. Just to set the structure that all branches/implementations should use to compare performance. While comparison between commits/branches should be easy, within is less trivial - e.g. comparing "Float64" with "Float32" across all operations doesn't work by judge-ing SUITE[@tagged ...].
Codecov Report
@@ Coverage Diff @@
## master #8 +/- ##
=====================================
- Coverage 100% 0% -100%
=====================================
Files 2 1 -1
Lines 30 1 -29
=====================================
- Hits 30 0 -30
- Misses 0 1 +1
Continue to review full report at Codecov.
|
Assign each function a unique name to avoid calling the wrong function with foo (as before) s.t. the whole thing runs smoothly.
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.
Benchmarks everything from the possible features with naive julia
implementations. Just to set the structure that all
branches/implementations should use to compare performance. While
comparison between commits/branches should be easy, within is less
trivial - e.g. comparing "Float64" with "Float32" across all operations
doesn't work by judge-ing SUITE[@tagged ...].
Could be merged to any branch that requires a benchmark-suite as soon as we're happy with the design.