Ryan Levick
Ryan Levick
The site sort of works on mobile, but the experience isn't great. We should improve this.
If a build fails to build, and there's a PR associated with that build, we should post a comment in that PR, indicating as such. Based on a conversation had...
The definition of a “mixed” perf run result is pretty poor. If there is any positive results whatsoever, even if vastly outweighed by negative results, it’s considered mixed. We should...
I ran into an issue where I was querying for "instructions:u" on local data where the instructions data had not been collected (presumably due to missing support in WSL). The...
Currently there is a compiler test for https://github.com/rust-lang/rust/issues/65131 in [rust-lang/rust](https://github.com/rust-lang/rust/blob/5444aded02d198e8b82e9025420375b8a68d156e/src/test/ui/issues/issue-65131.rs), but the test suite for the compiler has no way of testing long running yet unsuccessful compiles. This is more...
It would be useful to also have the ability to run the perf suite on Windows. One open question would be whether this would run as often as the Linux...
We currently only offer minimal assistance in analysis on the comparison page: * Noisy benchmarks are marked as such (though confusingly, it doesn't matter if one benchmark/incr-cache-state is noisy, the...
#899 started to document the [database schema](https://github.com/rust-lang/rustc-perf/blob/8e4d3e789679c355fdee87c3f6669261266380d4/database/schema.md) for parts I was working on. We should finish documenting the rest.
This issue is an extension of https://github.com/rust-lang/rustc-perf/issues/937 which aims to add more clarity to the database schema. This issue uses the [new glossary](https://github.com/rust-lang/rustc-perf/issues/938) for terms. Please make sure to first...
Metrics that are inherently noisy are always classified as being noisy (i.e., every benchmark for wall-time is marked as noisy). This is _true_, but not very helpful. Perhaps we need...