Add CoreCLR runtime build for browser-wasm performance benchmarks#124786
Merged
ilonatommy merged 5 commits intodotnet:mainfrom Feb 25, 2026
Merged
Add CoreCLR runtime build for browser-wasm performance benchmarks#124786ilonatommy merged 5 commits intodotnet:mainfrom
ilonatommy merged 5 commits intodotnet:mainfrom
Conversation
ilonatommy
added
area-VM-coreclr
perf-pipeline
Contributor
|
Tagging subscribers to this area: @agocke |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds support for building CoreCLR runtime for browser-wasm performance benchmarks, enabling performance comparisons between CoreCLR and Mono runtimes on the WASM platform. The changes parameterize existing WASM build infrastructure to support both runtime flavors.
Changes:
- Parameterized
perf-wasm-prepare-artifacts-steps.ymlwithruntimeFlavorandartifactNameto support both Mono and CoreCLR - Added conditional artifact staging logic that copies different files based on runtime flavor (Mono needs full SDK + nugets, CoreCLR needs only runtime pack)
- Added new CoreCLR build job in
perf-wasm-build-jobs.ymlthat producesBrowserWasmCoreCLRartifacts
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| eng/pipelines/performance/templates/perf-wasm-prepare-artifacts-steps.yml | Added parameters for runtime flavor and artifact name; split artifact preparation into Mono-specific (full SDK) and CoreCLR-specific (runtime pack only) paths |
| eng/pipelines/performance/templates/perf-wasm-build-jobs.yml | Added CoreCLR build job alongside existing Mono job, with appropriate build arguments and artifact naming |
… nuget dirs for payload script.
maraf
reviewed
Feb 25, 2026
maraf
approved these changes
Feb 25, 2026
iremyux
pushed a commit
to iremyux/dotnet-runtime
that referenced
this pull request
Mar 2, 2026
…tnet#124786) This PR adds support for building and testing CoreCLR on browser-wasm in the performance pipeline, alongside the existing Mono builds. Changes: Add a new build job in `perf-wasm-build-jobs.yml` for CoreCLR targeting browser_wasm with artifact name BrowserWasmCoreCLR. Parameterize `perf-wasm-prepare-artifacts-steps.yml` with runtimeFlavor and artifactName to support both runtimes CoreCLR artifacts are smaller (only runtime pack needed) vs Mono (full SDK + nugets) This enables running wasm benchmarks with `--wasm-coreclr` to compare performance between the two runtimes.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds support for building and testing CoreCLR on browser-wasm in the performance pipeline, alongside the existing Mono builds.
Changes:
Add a new build job in
perf-wasm-build-jobs.ymlfor CoreCLR targeting browser_wasm with artifact name BrowserWasmCoreCLR.Parameterize
perf-wasm-prepare-artifacts-steps.ymlwith runtimeFlavor and artifactName to support both runtimesCoreCLR artifacts are smaller (only runtime pack needed) vs Mono (full SDK + nugets)
This enables running wasm benchmarks with
--wasm-coreclrto compare performance between the two runtimes.