dont' hardcode curves in the benchmarks
up until now, elliptic curves have been hardcoded in the benchmarks, forcing to run them on all supported curves...
this MR makes it possible to use only a subset of curves.
Note
when running the same commands from !104 (merged), minus the "inbreeding" ones which are not affected by this MR, the time goes from 12min 33sec to 4min 28sec
TODO
-
setup -
commit -
recoding -
fec -
linalg -
setup size -
field operations -
group operations
Note
because all the unticked bullet points above are far from critical to the paper and do require to measure all curves, i won't change these for now
Edited by STEVAN Antoine
Merge request reports
Activity
added 2 commits
added 5 commits
-
4f92c5e3...be3b6b93 - 3 commits from branch
main
- be814699 - Merge branch 'main' into fix-hardcoded-curve-benchmarks
- 62fbb881 - simplify
-
4f92c5e3...be3b6b93 - 3 commits from branch
added 2 commits
waiting for !104 (merged) to land this
mentioned in commit 4552d2af
added 3 commits
-
36508a60...0f43be24 - 2 commits from branch
main
- 4552d2af - Merge branch 'main' into fix-hardcoded-curve-benchmarks
-
36508a60...0f43be24 - 2 commits from branch
mentioned in commit d7e84161
Please register or sign in to reply