Skip to content

Commit 97f0571

Browse files
authored
Merge pull request #782 from pnkfelix/compiler-shrinkmem-sprint
post announcing rustc march sprint
2 parents ad49ffb + 4ba2784 commit 97f0571

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
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,
25+
* we need some centralized documentation for how to best use those tools to measure rustc's memory usage, and
26+
* we need concrete proposals for tasks that will drive activity during the sprint; we started up
27+
the [shrinkmem-sprint zulip][] ([public archive][shrinkmem-sprint archive]) to host conversations related to that.
28+
29+
Given the more narrow focus of this sprint, the Rust Compiler Team is interested
30+
in input from people with strong experience using Valgrind DHAT or Windows
31+
Performance Analyzer (or other tools) to help with identifying opportunities to
32+
reduce memory usage. If this sounds like you please drop by the
33+
[shrinkmem-sprint zulip][] and say hello!
34+
35+
[mtg-2020-12-04]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/99285steeringmeeting20201204PerformanceGoalsfor2020.html
36+
37+
[mtg-2021-01-15]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/79391planningmeeting20210115.html
38+
39+
[mtg-2021-01-29]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/95022steeringmeeting20210129.html
40+
41+
[mtg-2021-02-12]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/44925planningmeeting20210212.html
42+
43+
[shrinkmem-sprint zulip]: https://rust-lang.zulipchat.com/#narrow/stream/276895-t-compiler.2Fshrinkmem-sprint
44+
[shrinkmem-sprint archive]: https://zulip-archive.rust-lang.org/276895tcompilershrinkmemsprint/index.html

0 commit comments

Comments
 (0)