Basic test benchmark for WebAssembly integration. #216
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
This is not nearly as efficient as a native build of the transform binary, due to bugs such as http://crbug.com/853685 and golang/go#27462, but serves as a starting point for further investigation. There have been a few optimizations already: - Keeping one long-lived process open to amortize the bootstrapping cost across requests. - Batching the "requests" to the wasm code via Promise.all. (This can be seen by adding a log statement just before the call to exports.run in wasm_exec.js.) Another potential problem to investigate the cost of is the lack of cross-heap GC.
|
internal bug http://b/119071852 |
This excludes it from the Travis build, which is on go1.10 (since that is our current supported version).
alin04
approved these changes
Dec 14, 2018
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 is not nearly as efficient as a native build of the transform
binary, due to bugs such as http://crbug.com/853685 and
golang/go#27462, but serves as a starting
point for further investigation.
There have been a few optimizations already:
cost across requests.
be seen by adding a log statement just before the call to exports.run
in wasm_exec.js.)
Another potential problem to investigate the cost of is the lack of
cross-heap GC.