Answer: To do in-depth CPU tracing profiling of Zed, annotate functions with instrument, then compile Zed with `ZTRACING=1 cargo r --features tracy --release`, and open the profiler (tracy-profiler) to click zed in the list of `Discovered clients`. Status: Overdue (check was due 2026-11-20T13:44:15Z and has not succeeded) Entry: tool/zed/troubleshooting/in-depth-cpu-tracing-profiling Revision: 1 Digest: sha256:1924ecd5a191f12d (changes whenever the content changes) Timeline: Created: 2026-11-13T04:05:46Z Last changed: 2026-11-13T04:05:46Z Last verified: 2026-11-19T13:44:15Z Next check: 2026-11-20T13:44:15Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of compile command | ZTRACING=1 cargo r --features tracy --release | [1] | 2026-11-19 annotation attribute | instrument | [1] | 2026-11-19 profiler to open | tracy-profiler | [1] | 2026-11-19 release build recommendation | highly recommended | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/performance.md". https://zed.dev/docs/performance.md Role: primary. Accessed: 2026-11-19T13:44:15Z Quote: "compile Zed with `ZTRACING=1 cargo r --features tracy --release`" (Supports: compile command) Quote: "Annotate any function you need to appear in the profile with instrument." (Supports: annotation attribute) Quote: "Open the profiler (tracy-profiler), you should see zed in the list of `Discovered clients` click it." (Supports: profiler to open) Quote: "The release build is optional but highly recommended" (Supports: release build recommendation) Snapshot SHA-256: 4c391b7ef539239f478a48e218ca5a07d0da0cb21795f5518eae96f3c9c4863e (captured 2026-11-13T04:05:45Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T04:05:46Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:44:15Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:44:15Z Last attempt: 2026-11-19T13:44:15Z Notes and limitations: Extracted automatically from a single official source (section "In depth CPU profiling (Tracing)"). Human-readable page: https://zed.dev/docs/performance.html Related: https://latestn.com/tool/zed/troubleshooting/julia-extension-issues Where do I report issues with the Zed Julia extension? https://latestn.com/tool/zed/troubleshooting/lldb-dap-binary-lookup How does Zed find the lldb-dap binary for Swift debugging? https://latestn.com/tool/zed/troubleshooting/makefile-extension-issues Where do I report issues with the Makefile extension in Zed? https://latestn.com/tool/zed/troubleshooting/force-specific-gpu How do I force Zed to use a specific GPU or fix graphics issues on Linux? https://latestn.com/tool/zed/troubleshooting/generate-backtraces-from-minidump How do I generate backtraces from a Zed crash minidump? https://latestn.com/tool/zed/troubleshooting/graphics-issues-fails-to-launch How do I troubleshoot Zed failing to launch due to graphics issues on Windows? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:05:46Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling POST: https://latestn.com/dispute/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I do in-depth CPU tracing profiling of Zed? Revision 1, last verified 2026-11-19T13:44:15Z. https://latestn.com/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling (accessed 2026-11-21T09:58:30Z). @misc{LatestN_tool_zed_troubleshooting_in_depth_cpu_tracing_profiling_r1, title = {How do I do in-depth CPU tracing profiling of Zed?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling}}, note = {Revision 1; digest sha256:1924ecd5a191f12d; last verified 2026-11-19T13:44:15Z; accessed 2026-11-21T09:58:30Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/troubleshooting/in-depth-cpu-tracing-profiling