Removed mention of profilers, added a segue to debuginfo and add Cargo links

Author: Kobzol

content/rust-compiler-performance-survey-2025-results/index.md

@@ -158,13 +158,15 @@ A related aspect is the latency of type checking in code editors and IDEs. Aroun
 
 The maintainers of Rust Analyzer are working hard on improving its performance. Its caching system is [being improved][ra-talk-rustweek] to reduce analysis latency, the distributed builds of the editor are now [optimized with PGO][ra-pgo], which provided 15-20% performance wins, and work is underway to integrate the compiler's [new trait solver][ra-new-trait-solver] into Rust Analyzer, which could eventually also result in increased performance.
 
-More than 35% users said that they consider the IDE and Cargo blocking one another to be a big problem. There is an existing workaround for this, where you can configure Rust Analyzer to use a different target directory than Cargo, at the cost of increased disk space usage. We realized that this workaround has not been documented in a very visible way, so we added it to the [FAQ section][ra-cargo-blocking] of the Rust Analyzer book.
+More than 35% users said that they consider the IDE and Cargo [blocking one another][ra-cargo-blocking-issue] to be a big problem. There is an existing workaround for this, where you can configure Rust Analyzer to use a different target directory than Cargo, at the cost of increased disk space usage. We realized that this workaround has not been documented in a very visible way, so we added it to the [FAQ section][ra-cargo-blocking-faq] of the Rust Analyzer book.
 
 ### Clean and CI builds
 
 Around 20% of participants responded that clean builds are a significant blocker for them. In order to improve their performance, you can try a recently introduced experimental Cargo and compiler option called [`hint-mostly-unused`][hint-mostly-unused], which can in certain situations help improve the performance of clean builds, particularly if your dependencies contain a lot of code that might not actually be used by your crate(s).
 
-One area where clean builds might happen often is Continuous Integration (CI). 1495 respondents said that they use CI to build Rust code, and around 25% of them consider its performance to be a big blocker for them. However, almost 36% of respondents who consider CI build performace to be a big issue said that they do not use any caching in CI, which we found surprising. One explanation might be that the generated artifacts (the `target` directory) is too large for effective caching, and runs into usage limits of CI providers, which is something that we saw mentioned repeatedly in the open answers section. We have recently introduced an experimental Cargo and compiler option called [`-Zembed-metadata`][cargo-no-embed-metadata] that is designed to reduce the size of the `target` directory, which might help with this issue somewhat in the future.
+One area where clean builds might happen often is Continuous Integration (CI). 1495 respondents said that they use CI to build Rust code, and around 25% of them consider its performance to be a big blocker for them. However, almost 36% of respondents who consider CI build performace to be a big issue said that they do not use any caching in CI, which we found surprising. One explanation might be that the generated artifacts (the `target` directory) is too large for effective caching, and runs into usage limits of CI providers, which is something that we saw mentioned repeatedly in the open answers section. We have recently introduced an experimental Cargo and compiler option called [`-Zembed-metadata`][cargo-no-embed-metadata] that is designed to reduce the size of the `target` directories, and work is also underway to regularly [garbage collect][cargo-garbage-collect] them. This might help with the disk space usage issue somewhat in the future.
+
+One additional way to significantly reduce disk usage is to reduce the amount of generated debug information, which brings us to the next section.
 
 ## Debug information
 
@@ -185,11 +187,11 @@ However, if Rust developers debug their code after most builds, then this cost m
 </div>
 <!-- Chart debugger end -->
 
-Based on these results, it seems that the respondents of our survey do not actually use a debugger all that much[^why-not-debug]. Similarly, only 6% of respondents answered that they use a profiler (which also benefits from at least basic debuginfo) often.
+Based on these results, it seems that the respondents of our survey do not actually use a debugger all that much[^why-not-debug].
 
 [^why-not-debug]: Potentially because of the strong invariants upheld by the Rust type system, and partly also because the Rust debugging experience might not be optimal for many users, which is a feedback that we received in the [State of Rust 2024 survey][state-of-rust-2024].
 
-On the other hand, when we asked people if they require debuginfo to be generated by default, the responses were much less clear-cut:
+However, when we asked people if they require debuginfo to be generated by default, the responses were much less clear-cut:
 
 <!-- Chart required-debuginfo start -->
 <div>
@@ -304,6 +306,7 @@ We know that some people are wondering why it takes so much time to achieve prog
 [cargo-linker-timings]: https://github.com/rust-lang/cargo/pull/15923
 [cargo-no-embed-metadata]: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#no-embed-metadata
 [cargo-check-build-reuse-issue]: https://github.com/rust-lang/cargo/issues/3501
+[cargo-garbage-collect]: https://github.com/rust-lang/cargo/issues/13136
 [cache-proc-macros]: https://github.com/rust-lang/rust/pull/145354
 [rust-lld-blog-post]: https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable
 [project-goal-rdr]: https://rust-lang.github.io/rust-project-goals/2025h2/relink-dont-rebuild.html
@@ -316,7 +319,8 @@ We know that some people are wondering why it takes so much time to achieve prog
 [ra-talk-rustweek]: https://www.youtube.com/watch?v=tn6qwhMNBJo
 [ra-pgo]: https://github.com/rust-lang/rust-analyzer/pull/19582
 [ra-new-trait-solver]: https://github.com/rust-lang/rust-analyzer/pull/20329
-[ra-cargo-blocking]: https://rust-analyzer.github.io/book/faq.html#rust-analyzer-and-cargo-compete-over-the-build-lock
+[ra-cargo-blocking-issue]: https://github.com/rust-lang/cargo/issues/4282
+[ra-cargo-blocking-faq]: https://rust-analyzer.github.io/book/faq.html#rust-analyzer-and-cargo-compete-over-the-build-lock
 
 <!-- Chart scripts -->