From 002f225773c0f898ecd3bf6786b1d7f4aed0337a Mon Sep 17 00:00:00 2001 From: N Date: Fri, 22 Nov 2024 16:51:42 -0800 Subject: [PATCH] Update book/writing-programs/cycle-tracking.md Co-authored-by: Chris T. --- book/writing-programs/cycle-tracking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/writing-programs/cycle-tracking.md b/book/writing-programs/cycle-tracking.md index 488335fe4..ae99f9fe0 100644 --- a/book/writing-programs/cycle-tracking.md +++ b/book/writing-programs/cycle-tracking.md @@ -58,7 +58,7 @@ This will log the cycle count for `block name` and include it in the `ExecutionR ### Profiling a ZKVM program -Profiling a zkvm program is a good way to get an understanding of what is bottlenecking your program. Note only one program may be profiled at a time. +Profiling a zkVM program produces a profile ([example link](https://share.firefox.dev/3Om1pzz)) which makes it easy to examine program performance and see exactly where exactly VM cycles are being spent without needing to modify the program at all. To profile a program, you simply need to: 1. Enable the profiling feature for `sp1-sdk` in `script/Cargo.toml`