| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | feat(zkvms_guest_io): Add private and public input arguments | Kamen Mladenov | 2025-05-07 | 1 | -2/+11 |
| | | | | | | This allows us to pass custom inputs on single-guest commands (nix run .#fibonacci). | ||||
| * | fix(zkvms_guest_io): Expect instead of unwrap temporary files | Kamen Mladenov | 2025-05-02 | 1 | -2/+8 |
| | | |||||
| * | fix(zkvms_guest_io): Print a string above the command log | Kamen Mladenov | 2025-05-02 | 1 | -0/+1 |
| | | | | | | Thus, if a user sees "Command log" in their output, they'll be able to easily find where in the codebase the log is outputted. | ||||
| * | chore: nix fmt | Kamen Mladenov | 2025-05-02 | 1 | -15/+12 |
| | | |||||
| * | chore: cargo fmt | Kamen Mladenov | 2025-05-02 | 1 | -19/+24 |
| | | |||||
| * | feat(zkvms_guest_io): Output proof size | Kamen Mladenov | 2025-05-02 | 1 | -0/+6 |
| | | | | | | | | 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. | ||||
| * | feat(zkvms_guest_io): Output command error when it exits unsuccessfully | Kamen Mladenov | 2025-05-02 | 1 | -3/+9 |
| | | |||||
| * | feat(zkvms_guest_io): Add "metadata" fields to metrics output | Kamen Mladenov | 2025-05-02 | 2 | -6/+26 |
| | | | | | These are the zkvm name, rev, guest name and benchmarks repo rev | ||||
| * | feat(zkvms_guest_io): Add hardware information to metrics output | Kamen Mladenov | 2025-05-02 | 3 | -1/+319 |
| | | |||||
| * | fix(zkvms io): More detailed errors on metrics output failure | Kamen Mladenov | 2025-05-02 | 1 | -2/+2 |
| | | |||||
| * | feat(zkvms_guest_io): Track and output memory usage | Kamen Mladenov | 2025-05-02 | 2 | -10/+28 |
| | | | | | | | We're using benchexec's runexec to track how much memory our program uses. Because of nix compatibility troubles, for now we've disabled runexec's container feature. This could result in less accurate data. | ||||
| * | feat(zkvms_guest_io): Allow output to be emmited into a file | Kamen Mladenov | 2025-05-02 | 1 | -1/+30 |
| | | |||||
| * | feat(zkvms_guest_io): Run all operations and output json format | Kamen Mladenov | 2025-05-02 | 3 | -33/+68 |
| | | | | | | | | | | Following the new output format, we'll run the guest program for each zkVM, for each operation (execute, prove, verify with --benchmark flag). Then we'll combine the resultant JSON outputs into one big JSON object. For now we're only printing the result object. Later we'll add the ability to write it into any file. | ||||
| * | chore(zkvms_guest_io): Code style improvements | Kamen Mladenov | 2025-03-10 | 1 | -8/+15 |
| | | |||||
| * | feat(zkvms_guest_io): Make execution linear, instead of parallel | Kamen Mladenov | 2025-03-10 | 1 | -36/+24 |
| | | | | | | zkVMs are multithreaded, so having parallel execution will result in inconsistent results, as every zkVM is fighting for resources | ||||
| * | fix(zkvms_guest_io): Remove unnecessary panicking on failed command | Kamen Mladenov | 2025-03-10 | 1 | -5/+0 |
| | | |||||
| * | fix(zkvms_guest_io): Improve option error messages | Kamen Mladenov | 2025-03-10 | 1 | -2/+2 |
| | | |||||
| * | feat(zkvms_guest_io): Add the ability to fail all commands on a single failure | Kamen Mladenov | 2025-03-10 | 1 | -1/+21 |
| | | |||||
| * | feat: Replace guest script with a fully-fledged Rust program | Kamen Mladenov | 2025-03-10 | 4 | -0/+336 |
 |
index : blocksense/zkVMs-benchmarks | |
| Setups and programs for zero-knowledge virtual machine benchmarking |
| aboutsummaryrefslogtreecommitdiff |
path: root/zkvms_guest_io