Ensure execution_benchmarks download the profiler#7529
Merged
andrewlock merged 1 commit intoSep 19, 2025
Conversation
andrewlock
added
the
area:builds
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing the following branches/commits: Execution-time benchmarks measure the whole time it takes to execute a program. And are intended to measure the one-off costs. Cases where the execution time results for the PR are worse than latest master results are shown in red. The following thresholds were used for comparing the execution times:
Note that these results are based on a single point-in-time result for each branch. For full results, see the dashboard. Graphs show the p99 interval based on the mean and StdDev of the test run, as well as the mean value of the run (shown as a diamond below the graph). gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.8)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
This PR (7529) - mean (194ms) : 190, 199
. : milestone, 194,
master - mean (194ms) : 191, 198
. : milestone, 194,
section Baseline
This PR (7529) - mean (192ms) : 186, 197
. : milestone, 192,
master - mean (191ms) : 188, 194
. : milestone, 191,
section CallTarget+Inlining+NGEN
This PR (7529) - mean (1,106ms) : 1064, 1147
. : milestone, 1106,
master - mean (1,105ms) : 1069, 1141
. : milestone, 1105,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
This PR (7529) - mean (274ms) : 270, 279
. : milestone, 274,
master - mean (274ms) : 269, 278
. : milestone, 274,
section Baseline
This PR (7529) - mean (273ms) : 268, 279
. : milestone, 273,
master - mean (274ms) : 267, 280
. : milestone, 274,
section CallTarget+Inlining+NGEN
This PR (7529) - mean (895ms) : 857, 932
. : milestone, 895,
master - mean (890ms) : 864, 916
. : milestone, 890,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
This PR (7529) - mean (268ms) : 264, 271
. : milestone, 268,
master - mean (266ms) : 262, 271
. : milestone, 266,
section Baseline
This PR (7529) - mean (268ms) : 263, 273
. : milestone, 268,
master - mean (268ms) : 261, 274
. : milestone, 268,
section CallTarget+Inlining+NGEN
This PR (7529) - mean (878ms) : 830, 926
. : milestone, 878,
master - mean (875ms) : 834, 916
. : milestone, 875,
gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
This PR (7529) - mean (265ms) : 259, 272
. : milestone, 265,
master - mean (267ms) : 260, 273
. : milestone, 267,
section Baseline
This PR (7529) - mean (267ms) : 262, 272
. : milestone, 267,
master - mean (266ms) : 258, 273
. : milestone, 266,
section CallTarget+Inlining+NGEN
This PR (7529) - mean (782ms) : 756, 809
. : milestone, 782,
master - mean (786ms) : 764, 809
. : milestone, 786,
gantt
title Execution time (ms) FakeDbCommand (.NET Framework 4.8)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
master - mean (72ms) : 71, 73
. : milestone, 72,
section Baseline
master - mean (68ms) : 66, 71
. : milestone, 68,
section CallTarget+Inlining+NGEN
master - mean (1,006ms) : 977, 1035
. : milestone, 1006,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
master - mean (107ms) : 105, 108
. : milestone, 107,
section Baseline
master - mean (106ms) : 103, 108
. : milestone, 106,
section CallTarget+Inlining+NGEN
master - mean (704ms) : 686, 722
. : milestone, 704,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
master - mean (94ms) : 93, 95
. : milestone, 94,
section Baseline
master - mean (93ms) : 91, 96
. : milestone, 93,
section CallTarget+Inlining+NGEN
master - mean (666ms) : 648, 683
. : milestone, 666,
gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat X
axisFormat %s
todayMarker off
section Bailout
master - mean (93ms) : 91, 94
. : milestone, 93,
section Baseline
master - mean (92ms) : 90, 94
. : milestone, 92,
section CallTarget+Inlining+NGEN
master - mean (601ms) : 591, 612
. : milestone, 601,
|
andrewlock
deleted the
andrew/ci/ensure-profiler-is-there-in-benchmarks
branch
September 19, 2025 09:04
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
3 participants
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 of changes
Ensure the profiler files are available in the execution benchmarks
Reason for change
While working on #7287, we discovered that the profiler was not downloaded, which was causing a stable config PInvoke to fail. To more closely replicate customer environments, we should ensure the profiler is available in these benchmarks, as it will impact startup time etc.
Implementation details
Download the
windows-profiler-homeartifact. Note that thewindows-tracer-homeartifact is already available thanks to therestore-working-directorystep, so it's not necessary to re-download it.Test coverage
This is the test, we'll examine the benchmarks out of interest to see if there's any impact, but fundamentally this is the more "correct" behaviour anyway.
Other details
Blocks #7287