Answer: To improve performance on large Rust projects in Zed, disable or limit the check-on-save feature by setting rust-analyzer.checkOnSave to false, and optionally set cargo.allTargets to false and check.workspace to false in the lsp.rust-analyzer initialization_options in Zed's settings.json. The text notes that checkOnSave defaults to true and runs cargo check --workspace --all-targets on every save, which does not scale well. Status: Overdue (check was due 2026-11-20T13:43:18Z and has not succeeded) Entry: tool/zed/troubleshooting/rust-large-project-performance Revision: 1 Digest: sha256:e093ead3051f0bf1 (changes whenever the content changes) Timeline: Created: 2026-11-13T04:04:50Z Last changed: 2026-11-13T04:04:50Z Last verified: 2026-11-19T13:43:18Z Next check: 2026-11-20T13:43:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of checkOnSave default | true | [1] | 2026-11-19 check.workspace default | true | [1] | 2026-11-19 cargo.allTargets default | true | [1] | 2026-11-19 checkOnSave setting | false | [1] | 2026-11-19 cargo.allTargets setting | false | [1] | 2026-11-19 check.workspace setting | false | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/languages/rust.md". https://zed.dev/docs/languages/rust.md Role: primary. Accessed: 2026-11-19T13:43:18Z Quote: "rust-analyzer.checkOnSave (default: true)" (Supports: checkOnSave default) Quote: "rust-analyzer.check.workspace (default: true)" (Supports: check.workspace default) Quote: "rust-analyzer.cargo.allTargets (default: true)" (Supports: cargo.allTargets default) Quote: ""checkOnSave": false," (Supports: checkOnSave setting) Quote: ""allTargets": false" (Supports: cargo.allTargets setting) Quote: ""workspace": false" (Supports: check.workspace setting) Snapshot SHA-256: 157d484a9f34b920c91aefd4d004c226e71aff0254cabb7e106bf5906d85f12b (captured 2026-11-13T04:04:49Z) 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:04:50Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:43:18Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:43:18Z Last attempt: 2026-11-19T13:43:18Z Notes and limitations: Extracted automatically from a single official source (section "Large projects and performance"). Human-readable page: https://zed.dev/docs/languages/rust.html Related: https://latestn.com/tool/zed/troubleshooting/semantic-tokens-not-appearing Why are semantic tokens not appearing in Zed and how do I troubleshoot it? https://latestn.com/tool/zed/troubleshooting/shell-debugger-usage How do I run Zed under GDB or LLDB from a shell? https://latestn.com/tool/zed/troubleshooting/show-lsp-error-messages How do I show language server error messages in the Zed status bar? https://latestn.com/tool/zed/troubleshooting/roc-extension-issues Where do I report issues with the Roc extension in Zed? https://latestn.com/tool/zed/troubleshooting/rst-extension-issues Where do I report issues with the Zed reST extension? https://latestn.com/tool/zed/troubleshooting/run-visual-regression-tests How do I run Zed's visual regression tests on macOS? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:04:50Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/rust-large-project-performance/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/rust-large-project-performance POST: https://latestn.com/dispute/tool/zed/troubleshooting/rust-large-project-performance with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/rust-large-project-performance?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure rust-analyzer for large Rust projects to improve performance in Zed? Revision 1, last verified 2026-11-19T13:43:18Z. https://latestn.com/tool/zed/troubleshooting/rust-large-project-performance (accessed 2026-11-21T09:59:40Z). @misc{LatestN_tool_zed_troubleshooting_rust_large_project_performance_r1, title = {How do I configure rust-analyzer for large Rust projects to improve performance in Zed?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/rust-large-project-performance}}, note = {Revision 1; digest sha256:e093ead3051f0bf1; last verified 2026-11-19T13:43:18Z; accessed 2026-11-21T09:59:40Z} } 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/rust-large-project-performance