| Commit message (Collapse) | Author | Age | Lines | SHA | |
|---|---|---|---|---|---|
| * | feat(zkvms_guest_io): Add private and public input arguments | 2025-05-07 | -2/+11 | df83e8e | |
| | | | | | | This allows us to pass custom inputs on single-guest commands (nix run .#fibonacci). | ||||
| * | fix(zkvms_guest_io): Expect instead of unwrap temporary files | 2025-05-02 | -2/+8 | 59fe5b3 | |
| | | |||||
| * | fix(zkvms_guest_io): Print a string above the command log | 2025-05-02 | -0/+1 | dd07218 | |
| | | | | | | 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: cargo fmt | 2025-05-02 | -19/+24 | 1a2ad55 | |
| | | |||||
| * | feat(zkvms_guest_io): Output proof size | 2025-05-02 | -0/+6 | eefb57f | |
| | | | | | | | | 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 | 2025-05-02 | -3/+9 | 400c41f | |
| | | |||||
| * | feat(zkvms_guest_io): Add "metadata" fields to metrics output | 2025-05-02 | -4/+15 | ef3bec9 | |
| | | | | | These are the zkvm name, rev, guest name and benchmarks repo rev | ||||
| * | feat(zkvms_guest_io): Add hardware information to metrics output | 2025-05-02 | -1/+64 | e7ab4fd | |
| | | |||||
| * | fix(zkvms io): More detailed errors on metrics output failure | 2025-05-02 | -2/+2 | 42d9672 | |
| | | |||||
| * | feat(zkvms_guest_io): Track and output memory usage | 2025-05-02 | -6/+20 | 3a33696 | |
| | | | | | | | 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 | 2025-05-02 | -1/+30 | 2f8b3b3 | |
| | | |||||
| * | feat(zkvms_guest_io): Run all operations and output json format | 2025-05-02 | -32/+59 | 43b6a71 | |
| | | | | | | | | | | 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 | 2025-03-10 | -8/+15 | 9832b41 | |
| | | |||||
| * | feat(zkvms_guest_io): Make execution linear, instead of parallel | 2025-03-10 | -36/+24 | 8c3237c | |
| | | | | | | 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 | 2025-03-10 | -5/+0 | 821a5ea | |
| | | |||||
| * | fix(zkvms_guest_io): Improve option error messages | 2025-03-10 | -2/+2 | 18dd7f7 | |
| | | |||||
| * | feat(zkvms_guest_io): Add the ability to fail all commands on a single failure | 2025-03-10 | -1/+21 | 1808b61 | |
| | | |||||
| * | feat: Replace guest script with a fully-fledged Rust program | 2025-03-10 | -0/+64 | 5969acd | |
 |
index : blocksense/zkVMs-benchmarks | |
| Setups and programs for zero-knowledge virtual machine benchmarking |
| Website Summary Files Commits Branches @commit @diff @stats |