This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
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.
I ported the perf measurement script from
edge-js
, and took some measurements using release builds. Numbers are microseconds per function call, averaged over 100,000 iterations.Interpretation
napi-dotnet
is about twice as fast as edge-js, or 3x slower than plain in-engine JS function calls, in this scenario.napi-dotnet
AOT compiled build is consistently about 3% faster than the CLR build. I'd expect a greater difference for a smaller number of iterations, since AOT has the biggest impact on startup time.napi-dotnet
because it supports shared-memory typed-arrays and marshalling classes by reference, whereas edge-js serializes everything.