[ProfiledAOT] Update workflow to profile apps #9267
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The supported scenario for collecting profiles involves the diagnostics tools dotnet-trace and dotnet-dsrouter. To maintain a single step profile workflow, add a script to automatically record a trace.
mdh1418
force-pushed
the
new_profiled_aot_story
branch
from
2ec162e to
46e063b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #7722
.NET 7 introduced a newer Profiled AOT scenario for .NET apps running on mono runtime https://github.com/dotnet/runtime/blob/main/docs/design/mono/profiled-aot.md.
This PR aims to enable the Profiled AOT project to migrate from the legacy
aprofutilprofiler and follow the newer profiled AOT story while maintaining the single-step./dotnet-local.sh build src/ProfiledAot/build.projprofile generation.As the new profiled aot story involves diagnostics tools dotnet-trace and dotnet-dsrouter to collect a trace and bridge the trace collection process with the .NET running on a mobile device/emulator, an automated script is added to keep the number of steps minimal.
There is an issue (not yet created) with dotnet-pgo processing the .nettrace generated from tracing the maui app.