diff options
| author | Kamen Mladenov <kamen@syndamia.com> | 2025-04-30 17:25:15 +0300 |
|---|---|---|
| committer | Kamen Mladenov <kamen@syndamia.com> | 2025-05-02 15:32:54 +0300 |
| commit | eefb57f2c035be1a398f630dd8cfed8b4ccbe348 (patch) | |
| tree | 598cc4a5d784addf59bad7323018260b977ed6c2 /zkvms/zkm/host/src/main.rs | |
| parent | 400c41f4f408aee6002489633914cd74ca888ff4 (diff) | |
| download | zkVMs-benchmarks-eefb57f2c035be1a398f630dd8cfed8b4ccbe348.tar zkVMs-benchmarks-eefb57f2c035be1a398f630dd8cfed8b4ccbe348.tar.gz zkVMs-benchmarks-eefb57f2c035be1a398f630dd8cfed8b4ccbe348.zip | |
feat(zkvms_guest_io): Output proof size
In each zkVM we'll write the size to /tmp/proof_size and then guest_io
will read that value and place it inside our metrics output. This is not
the most elegant, and in certain zkVMs the file output is a part of the
benchmark timing, but it will have to do.
Diffstat (limited to 'zkvms/zkm/host/src/main.rs')
| -rw-r--r-- | zkvms/zkm/host/src/main.rs | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/zkvms/zkm/host/src/main.rs b/zkvms/zkm/host/src/main.rs index 3b8d068..1640b30 100644 --- a/zkvms/zkm/host/src/main.rs +++ b/zkvms/zkm/host/src/main.rs @@ -9,6 +9,7 @@ use zkm_sdk::{ use zkvms_host_io::{ benchmarkable, read_args, RunType::{Execute, Prove, Verify}, + output_proof_size, }; async fn get_proof( @@ -40,6 +41,8 @@ async fn prove( ) { let prover_result = get_proof(prover_client, prover_input).await; + output_proof_size(&prover_result); + prover_client .process_proof_results(&prover_result, &prover_input, &proof_results_path) .expect("process proof results error"); |