- 
                Notifications
    You must be signed in to change notification settings 
- Fork 5.2k
[PERF][iOS] Simplify iOS performance measurement scripts #120531
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
[PERF][iOS] Simplify iOS performance measurement scripts #120531
Conversation
- clearer naming of codegen/runtime variants - remove non strip symbols variants
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.
Pull Request Overview
This PR simplifies and standardizes iOS performance measurement scripts by refactoring naming conventions and removing duplicate measurements with different symbol stripping settings.
Key Changes
- Refactors artifact and display names to be more consistent and descriptive
- Removes redundant build configurations that only differed by the STRIP_DEBUG_SYMBOLSsetting
- Standardizes comment casing throughout build scripts
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description | 
|---|---|
| src/mono/sample/iOS/Makefile | Removes unused HYBRID_GLOBALIZATION parameter and related build configuration | 
| eng/pipelines/performance/templates/perf-ios-scenarios-build-jobs.yml | Removes hybridGlobalization parameter from build template | 
| eng/pipelines/performance/templates/build-perf-sample-apps.yml | Major refactoring of iOS build configurations, removing duplicate builds and standardizing naming | 
| Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival | 
Co-authored-by: Copilot <[email protected]>
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.
Looks good. I think the release/10.0 branch will need some of these types of updates as well, so once we have mostly settled these for a bit, we should update the release/10.0 branch to get it working as well.
| The diagnostic failure is unrelated and is failing on main as well https://dev.azure.com/dnceng-public/public/_build/results?buildId=1168122&view=logs&j=99a40162-d9e8-55f4-b01d-4be4f1208c7a&t=a2060ea1-f616-5d11-98a7-dfd0dac99e77 | 
Associated dotnet/performance PR: dotnet/performance#5007
Test run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2810833