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

investigate compile-time regressions from 2016-08-17 #35805

Closed
nikomatsakis opened this issue Aug 18, 2016 · 2 comments
Closed

investigate compile-time regressions from 2016-08-17 #35805

nikomatsakis opened this issue Aug 18, 2016 · 2 comments
Assignees
Labels
I-compiletime Issue: Problems and improvements with respect to compile times. P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@nikomatsakis
Copy link
Contributor

We don't really know what caused it, but http://perf.rust-lang.org/ reveals:

  • 25% drop on issue-32278-big-array-of-strings

and smaller drops on a number of other tests. Merits investigation.

@nikomatsakis nikomatsakis added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Aug 18, 2016
@nikomatsakis nikomatsakis added I-compiletime Issue: Problems and improvements with respect to compile times. P-high High priority labels Aug 18, 2016
@eddyb
Copy link
Member

eddyb commented Aug 23, 2016

We have more accurate stats for the switch to MIR, thanks to @Mark-Simulacrum.

EDIT: irrelevant for the observed range here.

@eddyb
Copy link
Member

eddyb commented Aug 24, 2016

Looking at this graph:

Everything else appears to be noise (similar on all benchmarks), nothing to do here!

@eddyb eddyb closed this as completed Aug 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-compiletime Issue: Problems and improvements with respect to compile times. P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants