Implement a custom Data.Iterator #3849
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
added 2 commits
July 28, 2016 18:44
This iterator uses an inline 32-byte buffer so it doesn't have to call copyBytes(to:count:) for every single byte. It results in an approximate 6x speedup on my computer.
1 task
|
@swift-ci Please smoke test |
|
For the benchmark? I called it Data because I think there are other legitimate benchmarks that might be written around Data and if they get written they should presumably go in the same file. |
|
@kballard We have in general been using separate benchmark files. See all the string benchmarks. |
|
The general principle of the benchmark suite is 1 benchmark per file. If there is common infrastructure, we move it to utils or something along those lines. |
|
I've submitted #3865 to rename the benchmark. |
|
@kballard Thanks! |
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.
What's in this pull request?
Implement a custom
Data.Iteratorinstead of using the defaultIndexingIterator. This custom iterator uses an internal 32-byte buffer so it doesn't have to callcopyBytes(to:count:)as often. This results in an approximate 6x speedup on my computer.With the included benchmark, I get the following numbers with
IndexingIterator:And the following numbers with the custom iterator:
This is a re-submission of #3831.
Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
A smoke test on macOS does the following:
device standard libraries are not built.
version of these tests are not run.
A smoke test on Linux does the following:
tests are not run.
Validation Testing
Lint Testing
Note: Only members of the Apple organization can trigger swift-ci.