| Commit message (Collapse) | Author | Age | Lines | SHA |
| |
|
|
|
| |
The usages of this flag were removed when we introduced our JSON metrics
format.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
appropriate
If we're not appending to a file with contents, then when we write our
data, we're going to be overwriting the old data. If the old data is
longer than the new one, we'll have some leftover text in the end, which
will cause a problem with JSON parsing.
We'll be truncating the file (i.e. emptying it out), but only when not
appending to it.
|
| | |
|
| | |
|
| |
|
|
| |
zkvsm_host_io lib
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
milliseconds flag
|
| | |
|
| | |
|
| |
|
|
| |
foreach_public_input_field macros
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
from TOML file
|
| |
|