Closed Uxio0 closed 2 years ago
Hi @carver just quoting for making sure this is the right place for the issue, as this repo was not updated for some time
Hi @carver just quoting for making sure this is the right place for the issue, as this repo was not updated for some time
Yeah, this is the right place for it. Thanks for the clear writeup!
I would review a PR that tries to address the issue. I don't have the opportunity to look into it myself right now, unfortunately.
I would review a PR that tries to address the issue. I don't have the opportunity to look into it myself right now, unfortunately.
Awesome. Could you point me to that PR? I cannot find it on this repo
To be more clear: if someone were to create a PR, I would review it 😄
To be more clear: if someone were to create a PR, I would review it 😄
Nice, then https://github.com/ethereum/eth-hash/pull/36
closed by #36... thanks @Uxio0 👌
What is wrong?
When optimizing code, we detected there's a long time spent on
Web3.keccak
method, so we tried to find some information about what's happening ` We runned a benchmark and were shocked about the results (results are in seconds for 500000 keccak):When setting
ETH_HASH_BACKEND="pysha3"
:Code that produced the error
How can it be fixed?
There should be something wrong for this big difference between the native libraries and
eth-hash