Today, I am pleased to announce the new Rust Compiler Performance Working Group!
The purpose of this working group is threefold:
- MEASURE The group will keep watch over how fast the Rust compiler is in the most common usage scenarios. This includes defining which scenarios those are and then, for each of them, defining a benchmark that allows us to measure how well we are doing. Eventually, we will have a compiler performance dashboard (based on perf.rlo) that (hopefully) will show compilation time graph lines steeply plummeting towards zero as Rust version numbers increase.
- COORDINATE The group will keep track of the compiler’s implementation, as far as its performance is concerned, and the manifold opportunities and ideas for making it faster. To this end, as the group’s lead, I will curate and keep up-to-date the Compiler Performance Tracking Issue that serves as a landing page for all things compiler performance and will make discoverable the many things people do in order to make the Rust compiler faster and more efficient.
- COMMUNICATE The group acts as a communication channel for its members, and to its members. There is the @rust-lang/WG-compiler-performance GitHub team for bringing relevant GitHub issues to the group’s attention. And there is the WG-compiler-performance Gitter channel that members of the group and interested individuals are invited to join.
The working group consists of what I think is a healthy mix of old hands who know the ins and outs of the Rust compiler; of more recent contributors who have nonetheless already left their mark on our compile-time graphs; of people who have experience building large and complicated Rust projects; and of people who know about profiling code and measuring performance in general. If you think you can contribute and are interested in joining, let me know in the comments below or drop me a line on the Gitter channel!
Let’s make this a great year for compiling Rust programs!