steering mtg: perf.rlo discussion
Meeting proposal info
- Title: perf.rlo discussion
- Type: technical
Summary
Let's review the perf.rust-lang.org web site. Specifically, lets spell out the goals and how they should be prioritized, and then use that prioritization to figure out what changes we might make.
For example, I think the compare page shows too many benchmarks without a clear indication of which ones are important and which ones can be ignored.
It has also been suggested that we might filter the data by default so that benchmarks with insignificant deltas are not included in the presentation.
XXX: Write about your idea here -- just a few sentences is enough! Better yet, add a link to a gist or hackmd document with more details.
Note that once the meeting is scheduled, we may request that you prepare some more details by the time the meeting takes place (ideally, by some time before, if you would like folks to review them).
About this issue
This issue corresponds to a meeting proposal for the compiler team steering meeting. It corresponds to a possible topic of discussion. You can read more about the steering meeting procedure here.
Comment policy
These issues are meant to be used as an "announcements channel" regarding the proposal, and not as a place to discuss the technical details. Feel free to subscribe to updates. We'll post comments when reviewing the proposal in meetings or making a scheduling decision. In the meantime, if you have questions or ideas, ping the proposers on Zulip (or elsewhere).
We had this meeting: https://zulip-archive.rust-lang.org/238009tcompilermeetings/11129designmeeting20210205perfrlosite.html
So I'm going to leave this open (as a reminder that it needs a writeup) but add the meeting-scheduled label so I stop thinking that we need to schedule it again.
The public zulip archive will be our record for this meeting: https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bdesign.20meeting.5D.202021-02-05.3A.20perf.2Erlo.20site/near/225303672