-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update & clean benchmarks #165
Conversation
632afad
to
fff19b5
Compare
@@ -38,8 +42,9 @@ fn generate_data(k: u32) -> Vec<Scalar> { | |||
|
|||
fn fft(c: &mut Criterion) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIS best_fft
can use different algorithms, depending on log_n <= log_threads
.
Asking myself if it's a good performance test if we do not control the number of threads here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm 🤔 I'd say it only makes sense to compare results when the number of threads used is the same (and therefore the same algorithm is used). It is true that this can show up as a weird trend when comparing the performance of the fft at different sizes in the same system.
c84dc2e
to
0d707d9
Compare
The PR looks good to me! @davidnevadoc |
Description
This PR is a general cleanup of the benchmarks.
Changes
bn256_field
->field_arith
group
->curve
less_than
benchmark.pairing
benchmark.bn256
in all benchmarks. ( All benchmarks are generic so they can be easily run for any other field or curve).