forked from microsoft/vscode-js-debug
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: use wasm content hash implementation (microsoft#288)
The hash speed was bugging me, particularly since we're soon going to need to hash files twice (as of microsoft#277) so last night I wanted to see if a webassembly version would fare better. Turns out it does. Hashing 1KB: ``` 7,520 ops/sec > current (1x) 72,500 ops/sec > wasm (9.64x) Benches: 2 Fastest: wasm Elapsed: 10.9s ``` The current JS algorithm only is hasing 7.5MB/s, which may sound like a decent amount, but remember some node_modules can be massive. This brings up a bit. ![](https://i.redd.it/tfugj4n3l6ez.png)
- Loading branch information
1 parent
ce91b48
commit 96fccf1
Showing
4 changed files
with
12 additions
and
111 deletions.
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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 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