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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launch the settings in the PGO harness #15631

Merged
merged 1 commit into from Jun 29, 2023
Merged

Conversation

DHowett
Copy link
Member

@DHowett DHowett commented Jun 29, 2023

When we moved the settings UI to lazy initialization in #15628, we broke PGO. Apparently, we were PGOing the tiny part of Settings that was being loaded on every launch (e.g. the XAML metadata provider 馃う)

Let's actually PGO launching the settings.

When we moved the settings UI to lazy initialization in #15628, we broke
PGO. Apparently, we were PGOing the tiny part of Settings that was
being loaded on every launch (e.g. the XAML metadata provider 馃う)

Let's actually PGO launching the settings.
@DHowett DHowett merged commit 80f2776 into main Jun 29, 2023
21 checks passed
@DHowett DHowett deleted the dev/duhowett/pgo-the-settings-ui branch June 29, 2023 20:48
@DHowett DHowett added this to To Cherry Pick in 1.18 Servicing Pipeline via automation Aug 14, 2023
@DHowett DHowett moved this from To Cherry Pick to Cherry Picked in 1.18 Servicing Pipeline Aug 14, 2023
DHowett added a commit that referenced this pull request Aug 14, 2023
When we moved the settings UI to lazy initialization in #15628, we broke
PGO. Apparently, we were PGOing the tiny part of Settings that was being
loaded on every launch (e.g. the XAML metadata provider 馃う)

Let's actually PGO launching the settings.

(cherry picked from commit 80f2776)
Service-Card-Id: 90213941
Service-Version: 1.18
@DHowett DHowett moved this from Cherry Picked to Shipped in 1.18 Servicing Pipeline Sep 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants