Open CPerezz opened 1 month ago
I just noticed an important thing. Unsure if it's related specifically to that. But I've tried a ton of configs and can't really tell any other cause.
Originally, with this PR I was getting ~4s prove_step calls. When my battery dropped to <25%, i got a performance regression of +5x. I was at ~27s per fold.
I'm not sure if this is expected. But it's definitely a pain point. I know having low battery doesn't help with performance. But wasn't expecting to get such a pitfall..
Does anyone know if that's a thing?
Could it be updated to fold >3 iterations? so that we can check that everything works fine when folding the output of the previous fold.
I wanted to wait for the 0xPARC folks to code the full thing to actually merge this. As I don't want to use my example as a test of correctness.
But I can update it if desired.
This PR resolves #155
The current approach, allows to:
prove_step
.load_witness
trait fn forFCircuit
.Current benchmarks situate the folding cost within the browser in arround 3.9s. Which is definitely not good. But better than the current status.
An example on how to use this can actually be seen at https://github.com/CPerezz/wasm-sonobe-integration