WIP: Benchmarks #29
Open
WIP: Benchmarks #29
Conversation
This file contains 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
- Make script executable - Add copyright notice - Add missing message sizes
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 adds a
pwboxbenchmarking script for Node and an HTML page for benchmarking in browsers. On my PC, benchmark yieldpwboxlatency of about 80 ms in Node and 130 ms in browsers:As expected, the size of the message plays almost no role on performance. Curiously enough, it seems that on Node 4, performance of the
tweetnaclimplementation falls ~10x after a couple of bench tests. Probably, has something to do with the shipped V8.Related to #2.