This repository was archived by the owner on Apr 29, 2020. It is now read-only.
test: adds benchmark test #11
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
ghost
assigned 
achingbrain
force-pushed
the
add-benchmark-test
branch
from
3796425 to
c574f45
Compare
achingbrain
force-pushed
the
add-benchmark-test
branch
from
c574f45 to
4863258
Compare
|
Some projects also have a |
|
...another thing that should be added to aegir |
Because it's useful to have this somewhere. Skipped because we can use this to do adhoc testing and don't want it to run as part of CI. It uses 'realistic' data sizes, so 64k incoming chunks and a 500MB file size. It passes zeroed buffers as using crypto to generate random bytes was a bottleneck and didn't seem to add much to the test. It runs the test 10 times then prints out the timing data collected while importing the file which you can then use to create graphs in Google Docs or whatever.
achingbrain
force-pushed
the
add-benchmark-test
branch
from
4863258 to
3576e1e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Because it's useful to have this somewhere. Skipped because we can use this to do adhoc testing and don't want it to run as part of CI.
It uses 'realistic' data sizes, so 64k incoming chunks and a 500MB file size.
It passes zeroed buffers as using crypto to generate random bytes was a bottleneck and didn't seem to add much to the test.
It runs the test 10 times then prints out the timing data collected while importing the file which you can then use to create graphs in Google Docs or whatever.