Add noble-hashes to benchmarks about hash-wasm HOT 12 CLOSED

Soon, noble-hashes would be extremely popular. Most ethereum projects should include it because it'll be included in "main lib".

We're waiting for the security audit now.

from hash-wasm.

Hey. I added it to my benchmark tool here: https://daninet.github.io/hash-wasm-benchmark/
Blake3 seems to be missing from the npm package. Feel free to create a PR to add a test for that as well.

from hash-wasm.

@Daninet readme is missing it though

from hash-wasm.

I try to keep the readme file short. I want to only add the most popular libraries on NPM and those which are based on WASM so they are comparable in performance.

from hash-wasm.

Okay, I will consider adding it to the next version.

from hash-wasm.

Thanks Dani!

from hash-wasm.

@Daninet I think it's unreasonable to benchmark toHex function. It slows down the benchmark by at least 40%. Can you remove the last line?

https://github.com/Daninet/hash-wasm-benchmark/blob/master/src/benchmark/sha256.worker.js#L56

I also don't see any util in manipulating an array of bytes in hex form instead of Uint8Array form.

from hash-wasm.

BTW, 0.3.0 is out, with blake3.

from hash-wasm.

To make the fair assessment, I ask for hexstring output from all libraries. In this way I make sure that I compare apples to apples.
Hexstring was chosen because all libraries does not support Uint8Array digests. Also hexstrings are still a very common and practical format for visualizing hashes.

from hash-wasm.

@Daninet i've sped up toHex conversion in 0.3 which would show more confident numbers in your benchmarks.

from hash-wasm.

Now I get incorrect hashes with 0.3 😢. My benchmark tool also compares the results...

from hash-wasm.

Fixed with 0.3.1 @Daninet

from hash-wasm.