Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why did syn-1.0.89 opt full suddenly get noisy? #1301

Open
pnkfelix opened this issue Apr 21, 2022 · 5 comments
Open

Why did syn-1.0.89 opt full suddenly get noisy? #1301

pnkfelix opened this issue Apr 21, 2022 · 5 comments

Comments

@pnkfelix
Copy link
Member

Spawned off of rust-lang/rust#96000 (comment)

It seems like syn-1.0.89 opt full suddenly became much noisier around 2022-04-17, and I do not know why:

image

I'm mostly filing this ticket because I'm uncomfortable saying "oh well that's life" while letting this benchmark continue to sit here and potentially flummox future performance triage efforts.

@nnethercote
Copy link
Contributor

Something relating to codegen unit boundaries, maybe?

@Mark-Simulacrum
Copy link
Member

Looks like indeed some major variability in LLVM query times -- so that's probably the right diagnosis. Unclear what actually caused that, though rust-lang/rust#96016 is the first bump on the graph -- it might be that preserving spans is making the symbol hash or something similar to it vary over time for something and as a result causing variability; I think we've seen something similar before.

@rylev
Copy link
Member

rylev commented Apr 26, 2022

Obviously the best thing to do here is to find the source of the noise, but should we consider not running this benchmark in the meantime (at least full builds)? This has shown up in many PRs as the only source of a perf regression and it causes confusion and makes folks trust the perf suite less.

@nnethercote
Copy link
Contributor

Shouldn't the confidence testing identify that this benchmark is noisy, and stop reporting it unless the changes are large enough?

@rylev
Copy link
Member

rylev commented Apr 26, 2022

Eventually, this might happen if the benchmark consistently bounces back and forth. However, it does take time for that noise to distribute through the historical data. I'm not sure when that will happen, but you might be right that we can afford to just wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants