Closed jafri closed 1 year ago
@jafri Did you directly call FC's alt_bn128_pair
or use the host function alt_bn128_pair
? I am going to reproduce the problem at our side.
Through compiled contract, not FC
@jafri I benchmarked FC
, Go
, and Rust
pairing functions (please see details in https://github.com/eosnetworkfoundation/mandel/issues/780). FC
paring is about 4 ms.
I am going to reproduce your results via contracts. I plan to base on our unittest code but would like to use the methods as close as possible to yours for the numbers.
[15,37,146,155,203,67,213,165,115,145 ...
. How are they mapped to the input to host function alt_bn128_pair
? Thanks.
Pass that data to the intrinsic alt_bn128_pair
inside any smart contract
Performance has been substantially improved in 4.0 via AntelopeIO/leap#461
input:
Takes 8-10ms per pair on jungle, might be worth optimizing if possible