You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's likely optimisations can be made on the prover and verifier side. For instance, we realised that it is cheaper for the verifier to compute all evaluations of a certain polynomial over the entire domain using an FFT and then select the ones of interest, than to individually evaluate that polynomial at the point of interest (we should implement a threshold to switch from one technique to the other).
Flamegraph is very useful in determining the bottlenecks.
I imagine similar optimisations to the above can be applied to more places.
The text was updated successfully, but these errors were encountered:
It's likely optimisations can be made on the prover and verifier side. For instance, we realised that it is cheaper for the verifier to compute all evaluations of a certain polynomial over the entire domain using an FFT and then select the ones of interest, than to individually evaluate that polynomial at the point of interest (we should implement a threshold to switch from one technique to the other).
Flamegraph is very useful in determining the bottlenecks.
I imagine similar optimisations to the above can be applied to more places.
The text was updated successfully, but these errors were encountered: