-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Reapply Support lazy instantiation of ProjectInstance values when CPS Evaluation cache is used #10350
Conversation
… Evaluation cache is used (dotnet#10030)" This reverts commit eade720.
…S Evaluation cache is used (dotnet#10030)" (dotnet#10205) This reverts commit 9bea802.
experimental insertion for checking the performance: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/563920 |
And yet another exp insertion: https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/567802 (as there were couple failed perf tests in previous that seems as noise to me - comparing to variance of previous main builds) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with the change:
- For the actual changes I defer to previous reviews (on Support lazy instantiation of ProjectInstance values when CPS Evaluation cache is used #10030)
- All 3 VS insertions haven't showed statistically significant degradation of perf in measured scenarios (there were some cases within variations - non of which showed on more than 1 run).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine by me if insertions are in good shape so we can isolate any regression this does cause.
Fixes AB#2067934
Context
A previous refactoring for performance optimization introduced a regression in memory usage in vcxprojreader (AB#2067934). Consequently, the new code was reverted until a fix was available. This PR contains the fix and reinstates the performance optimization code.
Changes Made
Testing
Manual verification of the impacted scenario.