Skip to content

Commit 3d17f7c

Browse files
committed
draft of post announcing rustc march sprint.
1 parent ad49ffb commit 3d17f7c

File tree

1 file changed

+42
-0
lines changed

1 file changed

+42
-0
lines changed
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
layout: post
3+
title: "March Sprint for rustc: Shrink Memory Usage"
4+
author: Felix Klock
5+
team: The Compiler Team <https://www.rust-lang.org/governance/teams/compiler>
6+
---
7+
8+
I am very excited about the compiler team's upcoming sprint, and
9+
I want to share that excitement with all of you.
10+
11+
The Rust Compiler Team decided over a series of recent meetings
12+
([4 dec 2020][mtg-2020-12-04], [15 jan 2021][mtg-2021-01-15],
13+
[29 jan 2021][mtg-2021-01-29]) that our focus for 2021 will be improving the compiler's
14+
performance from the perspective of the new contributor experience bootstrapping
15+
the compiler and developing code for the compiler.
16+
17+
The team's first sprint for 2021 will be during the first week of March, and its
18+
focus will be on reducing the memory footprint of the compiler during bootstrap.
19+
20+
During our most recent planning meeting ([12 feb 2021][mtg-2021-02-12]),
21+
there were no new significant steering meeting proposals, so we decided to
22+
do some extra sprint planning during that time. We established:
23+
24+
* we should settle on a common set of tools for measuring memory usage (for now we expect it to be Valgrind DHAT on Linux).
25+
* we need some centralized documentation for how to best use those tools to measure rustc's memory usage
26+
* we need concrete proposals for tasks that will drive activity during the sprint; we started up
27+
the [shrinkmem-sprint zulip][] to host conversations related to that.
28+
29+
One detail about this sprint that differs a little from previous rust hacking sessions like "impl days":
30+
we are not actively trying to solicit new contributors during this time. (Of course new contributors are
31+
always welcome to join in the fun, but the compiler team recognized that we do not have as much mentoring
32+
bandwwidth for this first sprint compared to past "impl days" events.)
33+
34+
[mtg-2020-12-04]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/99285steeringmeeting20201204PerformanceGoalsfor2020.html
35+
36+
[mtg-2021-01-15]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/79391planningmeeting20210115.html
37+
38+
[mtg-2021-01-29]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/95022steeringmeeting20210129.html
39+
40+
[mtg-2021-02-12]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/44925planningmeeting20210212.html
41+
42+
[shrinkmem-sprint zulip]: https://zulip-archive.rust-lang.org/276895tcompilershrinkmemsprint/index.html

0 commit comments

Comments
 (0)