[Profiler] Measure LibrariesInfoCache performance#8757
Conversation
9e35ac2 to
e194b7d
Compare
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (8757) and master. ✅ No regressions detected - check the details below Full Metrics ComparisonFakeDbCommand
HttpMessageHandler
Comparison explanationExecution-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 highlighted 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). Duration chartsFakeDbCommand (.NET Framework 4.8)gantt
title Execution time (ms) FakeDbCommand (.NET Framework 4.8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (74ms) : 70, 79
master - mean (73ms) : 69, 78
section Bailout
This PR (8757) - mean (77ms) : 75, 79
master - mean (77ms) : 75, 79
section CallTarget+Inlining+NGEN
This PR (8757) - mean (1,102ms) : 1047, 1157
master - mean (1,098ms) : 1045, 1151
FakeDbCommand (.NET Core 3.1)gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (116ms) : 109, 123
master - mean (114ms) : 108, 119
section Bailout
This PR (8757) - mean (114ms) : 111, 117
master - mean (114ms) : 110, 117
section CallTarget+Inlining+NGEN
This PR (8757) - mean (804ms) : 769, 839
master - mean (792ms) : 769, 815
FakeDbCommand (.NET 6)gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (101ms) : 98, 104
master - mean (100ms) : 97, 104
section Bailout
This PR (8757) - mean (102ms) : 99, 104
master - mean (104ms) : 98, 110
section CallTarget+Inlining+NGEN
This PR (8757) - mean (948ms) : 904, 992
master - mean (947ms) : 903, 991
FakeDbCommand (.NET 8)gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (102ms) : 97, 108
master - mean (100ms) : 95, 104
section Bailout
This PR (8757) - mean (101ms) : 97, 105
master - mean (100ms) : 98, 103
section CallTarget+Inlining+NGEN
This PR (8757) - mean (828ms) : 780, 875
master - mean (824ms) : 787, 862
HttpMessageHandler (.NET Framework 4.8)gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (199ms) : 195, 203
master - mean (197ms) : 193, 201
section Bailout
This PR (8757) - mean (203ms) : 200, 207
master - mean (201ms) : 198, 204
section CallTarget+Inlining+NGEN
This PR (8757) - mean (1,197ms) : 1157, 1236
master - mean (1,198ms) : 1154, 1243
HttpMessageHandler (.NET Core 3.1)gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (282ms) : 277, 288
master - mean (282ms) : 276, 288
section Bailout
This PR (8757) - mean (283ms) : 278, 288
master - mean (281ms) : 273, 289
section CallTarget+Inlining+NGEN
This PR (8757) - mean (957ms) : 937, 978
master - mean (955ms) : 933, 976
HttpMessageHandler (.NET 6)gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (275ms) : 268, 281
master - mean (275ms) : 271, 279
section Bailout
This PR (8757) - mean (276ms) : 268, 284
master - mean (275ms) : 270, 280
section CallTarget+Inlining+NGEN
This PR (8757) - mean (1,156ms) : 1113, 1199
master - mean (1,155ms) : 1125, 1186
HttpMessageHandler (.NET 8)gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8757) - mean (272ms) : 264, 280
master - mean (275ms) : 268, 281
section Bailout
This PR (8757) - mean (273ms) : 267, 278
master - mean (274ms) : 267, 280
section CallTarget+Inlining+NGEN
This PR (8757) - mean (1,036ms) : 990, 1082
master - mean (1,034ms) : 992, 1076
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BenchmarksBenchmark execution time: 2026-06-10 14:31:56 Comparing candidate commit fbfa097 in PR branch Found 0 performance improvements and 2 performance regressions! Performance is the same for 70 metrics, 0 unstable metrics, 59 known flaky benchmarks, 67 flaky benchmarks without significant changes.
|
af8c242 to
6c6dd0d
Compare
This comment has been minimized.
This comment has been minimized.
1683512 to
34fc14a
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1683512cdc
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Summary of changes
Add metrics to measure the cpu and memory consumption of the
LibrariesInfoCacheReason for change
We are add caches to the
LibrariesInfoCacheand we need to measure and watch the memory consumption.Implementation details
Add a
FootprintTrackerto track the cpu, memory.Use
MetricsRegistryto report them as profiling metrics.Test coverage
The tests we have should suffice.
Other details