-
Notifications
You must be signed in to change notification settings - Fork 263
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: Parallelise construction of perturbator coefficients at each l…
…evel (#10304) When constructing the perturbator via the tree technique we can parallelise the construction of the coefficients at each level which is one of the culprits of performance degrading when using an ambient trace of size 2^20. We see a ~1s improvement in performance doing this. 2^20 trace (`EXAMPLE_20`) in master for `ClientIVCBench/Full/6` was `38114 ms` and is now `37310 ms`. For the defacto `CLIENT_IVC_BENCH_STRUCTURE` which gives 2^19 finalised circuits we go from `29496ms` to `29188 ms` so not as impactful but also the performance doesn't degrade. I have also benchmarked the actual computation of coefficients and it is neglegible regardless of the ambient trace size (2^20 vs 2^19) .
- Loading branch information
1 parent
0311bf3
commit ba335bd
Showing
1 changed file
with
64 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ba335bd
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.
Possible performance regression was detected for benchmark 'C++ Benchmark'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
1.05
.wasmClientIVCBench/Full/6
95384.399199
ms/iter87862.19409100001
ms/iter1.09
This comment was automatically generated by workflow using github-action-benchmark.
CC: @ludamad @codygunton