-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: improve digest64 for as-sha256 #347
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
a7cde69
to
8168eda
Compare
the benchmark result in CI is not precise because it run with very short period of time, updated it to run at least 10s setBenchOpts({
minMs: 10000,
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to store build
artifacts in the repo?
yes, they are actually input for our typescript function every time we run, that's why they are tracked in git |
}, | ||
"devDependencies": { | ||
"@as-pect/assembly": "2.8.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can the file as-pect.config.js
be removed too?
Is this what you are referring to? Looks like we only care about Not part of this PR anyway, maybe something to be considered to improve the build process. |
checked the performance on a separate server and got same result to my local environment master feat4 mainnet
this branch
however benchmark result in CI consistently shows worse statistics so need to investigate this, may need to separate to smaller PRs in order to figure out the issue |
Motivation
Improve
digest64
Description
assemblyscript
yields better performancew
computation to the main loop inhashBlocks()
Uint8Array.slice()
Before:
After
digestTwoHashObjects
is ~10% faster anddigest64
is ~5% faster