Separate benchmarks #123
Merged
Separate benchmarks #123
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
…c addInPlace`), not a derived wrapper function (e.g. `func add` or `func +`, etc.) This also removed any previously added benchmarks. But not to worry we’ll add them back in a dedicated `SurgeBenchmarkTests` test target.
…ts/ArithmeticTests.swift`
…c logInPlace`), not a derived wrapper function (e.g. `func log`) This also removed any previously added benchmarks. But not to worry we’ll add them back in a dedicated `SurgeBenchmarkTests` test target.
…ts/LogarithmTests.swift`
Merged
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 starts moving Surge's benchmark tests into a separate
SurgeBenchmarkTeststarget.Currently Travis CI takes 8 - 10 min to run. The test suite alone takes about 40 sec on my local machine.
With a separate test bundle we will hopefully be able to reduce this significantly.
Further more tests now use arrays/vectors/matrices of size 1000/100/100 respectively for speed.
While benchmarks use arrays/vectors/matrices of size 100_000/1000/1000 respectively for accuracy.