From 5335bbeba4cedefe7140279b2ef59d700774cc03 Mon Sep 17 00:00:00 2001 From: "Abdel @ StarkWare" Date: Thu, 8 Aug 2024 11:57:47 +0200 Subject: [PATCH] =?UTF-8?q?=E2=9A=97=EF=B8=8F=20add=20machine=20info=20for?= =?UTF-8?q?=20benchmark=20sample=20run?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0c717e0..a1bace0 100644 --- a/README.md +++ b/README.md @@ -69,7 +69,9 @@ The benchmarks will be compiled with the ReleaseFast optimization level, providi ### Benchmark Results -The benchmark results are presented in a table format, displaying both nanosecond and millisecond timings: +The benchmark results are presented in a table format, displaying both nanosecond and millisecond timings. + +Example of a benchmark report: | Operation | Time (ns) | Time (ms) | | ---------------- | --------: | --------: | @@ -80,6 +82,18 @@ The benchmark results are presented in a table format, displaying both nanosecon | verify | 170793 | 0.171 | | End-to-End BDHKE | 992257 | 0.992 | +This run was performed on a MacBook Pro with an M1 chip. + +```bash +Machine Info: + Model: MacBook Pro + CPU: Apple M1 Max + Cores: 10 (Physical), 10 (Logical) + Memory: 64 GB + macOS Version: 14.5 + Zig Version: 0.14.0-dev.850+ddcb7b1c1 +``` + ### Benchmark Report When run with the `--report` option, a CSV file named `benchmark_report.csv` will be generated in the project root directory. This file contains the operation names and their corresponding execution times in nanoseconds.