Update scenarios README profiles to match current available profiles#2182
Open
LoopedBard3 wants to merge 1 commit into
aspnet:mainaspnet/Benchmarks:mainfrom
LoopedBard3:loopedbard3/update-scenario-profilesLoopedBard3/Benchmarks:loopedbard3/update-scenario-profilesCopy head branch name to clipboard
Open
Update scenarios README profiles to match current available profiles#2182LoopedBard3 wants to merge 1 commit intoaspnet:mainaspnet/Benchmarks:mainfrom LoopedBard3:loopedbard3/update-scenario-profilesLoopedBard3/Benchmarks:loopedbard3/update-scenario-profilesCopy head branch name to clipboard
LoopedBard3 wants to merge 1 commit into
aspnet:mainaspnet/Benchmarks:mainfrom
LoopedBard3:loopedbard3/update-scenario-profilesLoopedBard3/Benchmarks:loopedbard3/update-scenario-profilesCopy head branch name to clipboard
Conversation
The profiles table listed five EOL'd machines (aspnet-perf-lin, aspnet-perf-win, aspnet-citrine-lin, aspnet-citrine-win, aspnet-citrine-amd2) that were removed in aspnet#2169, and was missing aspnet-citrine-arm-win. Update the table to the current public profiles and repoint all sample commands that referenced retired profiles to aspnet-gold-lin/aspnet-gold-win. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates scenarios/README.md so the documented crank profiles and copy/paste sample commands reflect the profiles that actually exist in the repo’s aspnet.profiles*.yml files (removing retired “perf/citrine” profiles and switching examples to aspnet-gold-*, plus adding the ARM/Windows profile).
Changes:
- Removed retired profiles from the README profiles table and added
aspnet-citrine-arm-win. - Updated all sample
crankcommands to use existing profiles (aspnet-gold-lin/aspnet-gold-win) instead of retired ones.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
sebastienros
approved these changes
Jun 23, 2026
This file contains hidden or 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
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.
Summary
The
scenarios/README.mdProfiles section was out of date with the actual crank profiles defined inaspnet.profiles.yml/aspnet.profiles.standard.yml.Profiles table
aspnet-perf-lin,aspnet-perf-win,aspnet-citrine-lin,aspnet-citrine-win,aspnet-citrine-amd2.aspnet-citrine-arm-win(ARM/Windows, 80 cores) alongside the still-validaspnet-citrine-arm-lin,aspnet-gold-lin,aspnet-gold-win, andlocal.Sample commands
aspnet-perf-lin->aspnet-gold-linaspnet-perf-win/aspnet-citrine-win->aspnet-gold-winProfile names were validated against
scenarios/aspnet.profiles.ymlandscenarios/aspnet.profiles.standard.yml.