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.

Sign up for GitHub

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

Jump to bottom

[Perf] Triage backlog #92164

Open
DrewScoggins opened this issue Sep 15, 2023 · 6 comments
Open

[Perf] Triage backlog #92164

DrewScoggins opened this issue Sep 15, 2023 · 6 comments
Assignees
@DrewScoggins
Labels
area-Meta
Milestone
9.0.0

Comments

@DrewScoggins
Copy link
Member

7.0 -> 8.0-rc1 performance comparison

Ubuntu x64

Regressions

Windows x64

Regressions

Windows x86

Regressions

Ubuntu Arm64

Regressions

Windows Arm64

Regressions

WASM x64

Regressions

WASM AOT x64

Regressions

Mono AOT x64

Regressions
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 15, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Sep 15, 2023
@DrewScoggins DrewScoggins mentioned this issue Sep 15, 2023
Open
@ghost
Copy link

ghost commented Sep 18, 2023

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

7.0 -> 8.0-rc1 performance comparison

Ubuntu x64

Regressions

Windows x64

Regressions

Windows x86

Regressions

Ubuntu Arm64

Regressions

Windows Arm64

Regressions

WASM x64

Regressions

WASM AOT x64

Regressions

Mono AOT x64

Regressions

Author: DrewScoggins
Assignees: -
Labels:

area-Meta, untriaged, needs-area-label
Milestone: -

@jeffschwMSFT
Copy link
Member

adding additional folks, as this issue covers a lot of areas: @jeffhandley @ericstj @karelz

@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Sep 18, 2023
@ericstj
Copy link
Member

ericstj commented Sep 18, 2023

What's the goal of this issue? I thought there was already a triage process in place to look at these issues and move the meaningful ones over to dotnet/runtime: https://github.com/dotnet/runtime/issues/created_by/app/performanceautofiler

@jeffhandley
Copy link
Member

@DrewScoggins Is the perf triage v-team doing the initial investigation on these to determine which ones need to be transferred into dotnet/runtime?

My understanding is this report was produced as a means for comparing preview-to-rc all-up as another lens over the perf lab data that generally only auto-files issues on rolling build comparisons. Since we're not doing a manual perf run report this year, this preview-to-rc comparison is helpful for ensuring we didn't have gradual regressions go undetected. Is that correct, @DrewScoggins?

@DrewScoggins
Copy link
Member Author

The goal of this issue is to centralize all of the issues that during 8.0 for whatever reason didn't appear to be triaged. These were found by doing a 7.0 to 8.0-rc1 comparison and all regressions found checked against filed issues.

@DrewScoggins Is the perf triage v-team doing the initial investigation on these to determine which ones need to be transferred into dotnet/runtime?

This seems like the right way to handle working through these remaining issues.

My understanding is this report was produced as a means for comparing preview-to-rc all-up as another lens over the perf lab data that generally only auto-files issues on rolling build comparisons. Since we're not doing a manual perf run report this year, this preview-to-rc comparison is helpful for ensuring we didn't have gradual regressions go undetected. Is that correct, @DrewScoggins?

That is the main goal, yes. The other was to ensure that we had a final roll-up, and that we were sure that everything that we filed during 8.0 had been triaged.

@ericstj ericstj removed the untriaged New issue has not been triaged by the area owner label Sep 25, 2023
@ericstj ericstj added this to the 8.0.0 milestone Sep 25, 2023
@jeffhandley jeffhandley modified the milestones: 8.0.0, 9.0.0 Oct 24, 2023
@jeffhandley
Copy link
Member

Moving to 9.0.0 for further consideration of remaining unaddressed regressions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DrewScoggins DrewScoggins

Labels
area-Meta
Projects
None yet
Milestone
9.0.0
Development

No branches or pull requests
5 participants
@vcsjones @jeffhandley @ericstj @DrewScoggins @jeffschwMSFT