From 3d17f7c33a66c4b5807aa5a123c08c157036b0d6 Mon Sep 17 00:00:00 2001 From: "Felix S. Klock II" Date: Mon, 15 Feb 2021 21:27:42 -0500 Subject: [PATCH 1/3] draft of post announcing rustc march sprint. --- .../2021-02-15-shrinkmem-rustc-sprint.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md diff --git a/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md b/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md new file mode 100644 index 000000000..fb0824fb6 --- /dev/null +++ b/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md @@ -0,0 +1,42 @@ +--- +layout: post +title: "March Sprint for rustc: Shrink Memory Usage" +author: Felix Klock +team: The Compiler Team +--- + +I am very excited about the compiler team's upcoming sprint, and +I want to share that excitement with all of you. + +The Rust Compiler Team decided over a series of recent meetings +([4 dec 2020][mtg-2020-12-04], [15 jan 2021][mtg-2021-01-15], +[29 jan 2021][mtg-2021-01-29]) that our focus for 2021 will be improving the compiler's +performance from the perspective of the new contributor experience bootstrapping +the compiler and developing code for the compiler. + +The team's first sprint for 2021 will be during the first week of March, and its +focus will be on reducing the memory footprint of the compiler during bootstrap. + +During our most recent planning meeting ([12 feb 2021][mtg-2021-02-12]), +there were no new significant steering meeting proposals, so we decided to +do some extra sprint planning during that time. We established: + + * we should settle on a common set of tools for measuring memory usage (for now we expect it to be Valgrind DHAT on Linux). + * we need some centralized documentation for how to best use those tools to measure rustc's memory usage + * we need concrete proposals for tasks that will drive activity during the sprint; we started up + the [shrinkmem-sprint zulip][] to host conversations related to that. + +One detail about this sprint that differs a little from previous rust hacking sessions like "impl days": +we are not actively trying to solicit new contributors during this time. (Of course new contributors are +always welcome to join in the fun, but the compiler team recognized that we do not have as much mentoring +bandwwidth for this first sprint compared to past "impl days" events.) + +[mtg-2020-12-04]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/99285steeringmeeting20201204PerformanceGoalsfor2020.html + +[mtg-2021-01-15]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/79391planningmeeting20210115.html + +[mtg-2021-01-29]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/95022steeringmeeting20210129.html + +[mtg-2021-02-12]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/44925planningmeeting20210212.html + +[shrinkmem-sprint zulip]: https://zulip-archive.rust-lang.org/276895tcompilershrinkmemsprint/index.html From 64fe02fc2594b633c15345294d0bec94f1cd7a59 Mon Sep 17 00:00:00 2001 From: "Felix S. Klock II" Date: Mon, 15 Feb 2021 21:30:00 -0500 Subject: [PATCH 2/3] fix typo. --- posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md b/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md index fb0824fb6..42f7d9d2a 100644 --- a/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md +++ b/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md @@ -29,7 +29,7 @@ do some extra sprint planning during that time. We established: One detail about this sprint that differs a little from previous rust hacking sessions like "impl days": we are not actively trying to solicit new contributors during this time. (Of course new contributors are always welcome to join in the fun, but the compiler team recognized that we do not have as much mentoring -bandwwidth for this first sprint compared to past "impl days" events.) +bandwidth for this first sprint compared to past "impl days" events.) [mtg-2020-12-04]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/99285steeringmeeting20201204PerformanceGoalsfor2020.html From 4ba2784b77b526f216469042fce8aea1e550e1c6 Mon Sep 17 00:00:00 2001 From: "Felix S. Klock II" Date: Thu, 18 Feb 2021 09:50:01 -0500 Subject: [PATCH 3/3] review feedback. --- .../2021-02-15-shrinkmem-rustc-sprint.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md b/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md index 42f7d9d2a..5e230cb14 100644 --- a/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md +++ b/posts/inside-rust/2021-02-15-shrinkmem-rustc-sprint.md @@ -21,15 +21,16 @@ During our most recent planning meeting ([12 feb 2021][mtg-2021-02-12]), there were no new significant steering meeting proposals, so we decided to do some extra sprint planning during that time. We established: - * we should settle on a common set of tools for measuring memory usage (for now we expect it to be Valgrind DHAT on Linux). - * we need some centralized documentation for how to best use those tools to measure rustc's memory usage + * we should settle on a common set of tools for measuring memory usage, + * we need some centralized documentation for how to best use those tools to measure rustc's memory usage, and * we need concrete proposals for tasks that will drive activity during the sprint; we started up - the [shrinkmem-sprint zulip][] to host conversations related to that. + the [shrinkmem-sprint zulip][] ([public archive][shrinkmem-sprint archive]) to host conversations related to that. -One detail about this sprint that differs a little from previous rust hacking sessions like "impl days": -we are not actively trying to solicit new contributors during this time. (Of course new contributors are -always welcome to join in the fun, but the compiler team recognized that we do not have as much mentoring -bandwidth for this first sprint compared to past "impl days" events.) +Given the more narrow focus of this sprint, the Rust Compiler Team is interested +in input from people with strong experience using Valgrind DHAT or Windows +Performance Analyzer (or other tools) to help with identifying opportunities to +reduce memory usage. If this sounds like you please drop by the +[shrinkmem-sprint zulip][] and say hello! [mtg-2020-12-04]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/99285steeringmeeting20201204PerformanceGoalsfor2020.html @@ -39,4 +40,5 @@ bandwidth for this first sprint compared to past "impl days" events.) [mtg-2021-02-12]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/44925planningmeeting20210212.html -[shrinkmem-sprint zulip]: https://zulip-archive.rust-lang.org/276895tcompilershrinkmemsprint/index.html +[shrinkmem-sprint zulip]: https://rust-lang.zulipchat.com/#narrow/stream/276895-t-compiler.2Fshrinkmem-sprint +[shrinkmem-sprint archive]: https://zulip-archive.rust-lang.org/276895tcompilershrinkmemsprint/index.html