Skip to content

Commit 9f2ca2d

Browse files
committed
Add CTA to the beginning of the post and add survey link
1 parent 14ca33b commit 9f2ca2d

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ team = "the Compiler Performance Working Group"
88
team_url = "https://www.rust-lang.org/governance/teams/compiler#team-wg-compiler-performance"
99
+++
1010

11+
We're launching a [Rust Compiler Performance Survey][survey-link].
12+
1113
Long compile times of Rust code are frequently being cited as one of the biggest [challenges][annual-survey] limiting the productivity of Rust developers. Rust compiler contributors are of course aware of that, and they are continuously working to improve the situation, by finding [new ways][how-to-speed-up-the-compiler] of speeding up the compiler, [triaging performance regressions][performance-triage] and [measuring][perf-dashboard] our long-term performance improvements. Recently, we also made progress on some [large changes][stabilize-lld] that have been in the making for a long time, which could significantly improve compiler performance by default.
1214

1315
When we talk about compilation performance, it is important to note that it is not always so simple as determining how long does it take `rustc` to compile a crate. There are many diverse development workflows that might have competing trade-offs, and that can be bottlenecked by various factors, such as the integration of the compiler with the used build system.
@@ -16,12 +18,12 @@ In order to better understand these workflows, we have prepared a [Rust Compiler
1618

1719
**You can fill out the survey [here][survey-link].**
1820

19-
Filling the survey will likely take you approximately 10 minutes, and the survey is fully anonymous. We will accept submissions until Monday, July 7th, 2025. After the survey ends, we will evaluate the results and post key insights on this blog.
21+
Filling the survey should take you approximately 10 minutes, and the survey is fully anonymous. We will accept submissions until Monday, July 7th, 2025. After the survey ends, we will evaluate the results and post key insights on this blog.
2022

2123
We invite you to fill the survey, as your responses will help us improve Rust compilation performance. Thank you!
2224

2325
[annual-survey]: https://blog.rust-lang.org/2025/02/13/2024-State-Of-Rust-Survey-results/#challenges
24-
[survey-link]: TODO
26+
[survey-link]: https://www.surveyhero.com/c/rust-compiler-performance-2025
2527
[how-to-speed-up-the-compiler]: https://nnethercote.github.io/2025/03/19/how-to-speed-up-the-rust-compiler-in-march-2025.html
2628
[performance-triage]: https://github.com/rust-lang/rustc-perf/blob/master/triage/README.md
2729
[perf-dashboard]: https://perf.rust-lang.org/dashboard.html

0 commit comments

Comments
 (0)