-
-
Notifications
You must be signed in to change notification settings - Fork 17.2k
Up to 7% regression in recent rollup #57115
Copy link
Copy link
Closed
Labels
I-compilememIssue: Problems and improvements with respect to memory usage during compilation.Issue: Problems and improvements with respect to memory usage during compilation.I-compiletimeIssue: Problems and improvements with respect to compile times.Issue: Problems and improvements with respect to compile times.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.Performance or correctness regression from stable to nightly.
Description
Activity
Metadata
Metadata
Assignees
Labels
I-compilememIssue: Problems and improvements with respect to memory usage during compilation.Issue: Problems and improvements with respect to memory usage during compilation.I-compiletimeIssue: Problems and improvements with respect to compile times.Issue: Problems and improvements with respect to compile times.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.Performance or correctness regression from stable to nightly.
Noticed here it looks like something in that rollup has caused a blanket regression in compile time instruction counts while also simultaneously improving memory. The current hypothesis is that #56986 is incorrect and disabled jemalloc entirely.
Another hypothesis is that #56944 had a really weird effect on the build.
In any case, we should investigate!