Closed andrewlock closed 4 weeks ago
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) FakeDbCommand (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5970) - mean (73ms) : 63, 83
. : milestone, 73,
section CallTarget+Inlining+NGEN
This PR (5970) - mean (1,034ms) : 1012, 1057
. : milestone, 1034,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5970) - mean (109ms) : 106, 113
. : milestone, 109,
section CallTarget+Inlining+NGEN
This PR (5970) - mean (722ms) : 695, 750
. : milestone, 722,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5970) - mean (96ms) : 89, 102
. : milestone, 96,
section CallTarget+Inlining+NGEN
This PR (5970) - mean (675ms) : 651, 700
. : milestone, 675,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5970) - mean (190ms) : 188, 192
. : milestone, 190,
section CallTarget+Inlining+NGEN
This PR (5970) - mean (1,115ms) : 1095, 1136
. : milestone, 1115,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5970) - mean (276ms) : 271, 280
. : milestone, 276,
section CallTarget+Inlining+NGEN
This PR (5970) - mean (875ms) : 853, 898
. : milestone, 875,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (5970) - mean (265ms) : 259, 270
. : milestone, 265,
section CallTarget+Inlining+NGEN
This PR (5970) - mean (872ms) : 853, 891
. : milestone, 872,
Branch report: andrew/matang/exception-replay-testing-suite-v2
Commit report: a6842de
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 44 Passed, 0 Skipped, 28m 8.47s Total Time :hourglass: 14 Performance Regressions
This report shows up to 5 performance regressions.
Profiler_cpu_walltime_old_stackwalk
-scenarios
3.23s (+891.7ms, +38%) - DetailsProfiler_cpu_walltime
-scenarios
3.24s (+894.9ms, +38%) - DetailsProfiler_walltime
-scenarios
3.25s (+901.45ms, +38%) - DetailsProfiler_cpu_walltime_timer_create
-scenarios
3.24s (+901.78ms, +38%) - DetailsProfiler_liveheap
-scenarios
4.21s (+1.03s, +32%) - Details
Benchmarks for #5970 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Throughput results for AspNetCoreSimpleController comparing the following branches/commits:
Cases where throughput results for the PR are worse than latest master (5% drop or greater), results are shown in red.
Note that these results are based on a single point-in-time result for each branch. For full results, see one of the many, many dashboards!
gantt
title Throughput Linux x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5970) (11.189M) : 0, 11188782
master (11.115M) : 0, 11114864
benchmarks/2.9.0 (11.120M) : 0, 11120231
section Automatic
This PR (5970) (7.511M) : 0, 7510928
master (7.311M) : 0, 7311158
benchmarks/2.9.0 (7.874M) : 0, 7874046
section Trace stats
master (7.660M) : 0, 7659733
section Manual
This PR (5970) (9.684M) : crit ,0, 9683897
master (11.297M) : 0, 11296697
section Manual + Automatic
This PR (5970) (7.079M) : 0, 7079074
master (6.770M) : 0, 6770096
gantt
title Throughput Linux arm64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5970) (9.661M) : 0, 9661049
benchmarks/2.9.0 (9.342M) : 0, 9341974
section Automatic
This PR (5970) (6.652M) : 0, 6651809
section Manual
This PR (5970) (8.268M) : 0, 8268116
section Manual + Automatic
This PR (5970) (6.242M) : 0, 6241600
gantt
title Throughput Windows x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (5970) (10.012M) : 0, 10012186
master (10.030M) : 0, 10029859
benchmarks/2.9.0 (10.105M) : 0, 10105239
section Automatic
This PR (5970) (6.547M) : 0, 6546926
master (6.746M) : 0, 6746187
benchmarks/2.9.0 (7.518M) : 0, 7517801
section Trace stats
master (7.324M) : 0, 7323510
section Manual
This PR (5970) (8.671M) : crit ,0, 8670666
master (9.931M) : 0, 9931035
section Manual + Automatic
This PR (5970) (6.390M) : 0, 6389559
master (6.245M) : 0, 6244786
Added the infrastructure of integration testing for Exception Replay in ASP.NET Core.
To add a test, one needs to simply create a class that inherits from
IRun
/IAsyncRun
and decorated withExceptionReplayTestData
attribute, providing to the attribute the amount of snapshots anticipated both in default configuration and full stack trace capture configuration.This PR also introduces the renaming of the configs of Exception Replay from Exception Debugging. In the early days we used to call Exception Replay internally Exception Debugging, thus some of the configs held this name. This PR renamed those leftovers to Exception Replay, including the enablement config of
DD_EXCEPTION_REPLAY_ENABLED
. Introduced a PR todd-go
too where these configs were added to theconfig_norm_rules.json
file.Laying the groundwork for integration testing of Exception Replay.
The testing infra bootstraps the web app, queries via reflection all the tests (classes inheriting from
IRun
/IAsyncRun
and decorated withExceptionReplayTestData
attribute) and list them. Upon executing a test, a request will hit an endpoint ofRunTest
with the name of the test to run (FQN of the class name). The crafted test must throw an exception to be considered valid. For a more complex test scenarios, more endpoints could be introduced.Every test runs in 4 flavors:
This whole PR 🤓. I've added two tests that utilize the infra:
ExceptionWithNonSupportedFramesTest
RecursiveExceptionTest
Fixes DEBUG-2681, DEBUG-2732, DEBUG-1642.
Backport of https://github.com/DataDog/dd-trace-dotnet/pull/5821