-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Crashtracker] Fix missing GetThreadDescription symbol #6357
Conversation
f73ce70
to
594da42
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Datadog ReportBranch report: ✅ 0 Failed, 457196 Passed, 3239 Skipped, 21h 16m 26.59s Total Time |
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) FakeDbCommand (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6357) - mean (76ms) : 72, 81
. : milestone, 76,
master - mean (69ms) : 67, 70
. : milestone, 69,
section CallTarget+Inlining+NGEN
This PR (6357) - mean (1,036ms) : crit, 1010, 1062
. : crit, milestone, 1036,
master - mean (975ms) : 954, 996
. : milestone, 975,
gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6357) - mean (120ms) : 114, 126
. : milestone, 120,
master - mean (108ms) : 105, 110
. : milestone, 108,
section CallTarget+Inlining+NGEN
This PR (6357) - mean (728ms) : crit, 710, 746
. : crit, milestone, 728,
master - mean (679ms) : 666, 691
. : milestone, 679,
gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6357) - mean (102ms) : 96, 107
. : milestone, 102,
master - mean (91ms) : 88, 94
. : milestone, 91,
section CallTarget+Inlining+NGEN
This PR (6357) - mean (677ms) : crit, 660, 694
. : crit, milestone, 677,
master - mean (630ms) : 615, 646
. : milestone, 630,
gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.6.2)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6357) - mean (190ms) : 185, 195
. : milestone, 190,
master - mean (190ms) : 186, 194
. : milestone, 190,
section CallTarget+Inlining+NGEN
This PR (6357) - mean (1,104ms) : 1070, 1137
. : milestone, 1104,
master - mean (1,094ms) : 1064, 1124
. : milestone, 1094,
gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6357) - mean (276ms) : 274, 279
. : milestone, 276,
master - mean (277ms) : 272, 282
. : milestone, 277,
section CallTarget+Inlining+NGEN
This PR (6357) - mean (874ms) : 848, 899
. : milestone, 874,
master - mean (871ms) : 837, 906
. : milestone, 871,
gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat X
axisFormat %s
todayMarker off
section Baseline
This PR (6357) - mean (267ms) : 262, 271
. : milestone, 267,
master - mean (266ms) : 261, 271
. : milestone, 266,
section CallTarget+Inlining+NGEN
This PR (6357) - mean (855ms) : 814, 895
. : milestone, 855,
master - mean (851ms) : 810, 893
. : milestone, 851,
|
594da42
to
f09ad5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Benchmarks Report for tracer 🐌Benchmarks for #6357 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored. Benchmark detailsBenchmarks.Trace.ActivityBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.AgentWriterBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.AspNetCoreBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.DbCommandBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.ElasticsearchBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.GraphQLBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.HttpClientBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.ILoggerBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.Log4netBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.NLogBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.RedisBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.SerilogBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.SpanBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.TraceAnnotationsBenchmark - Same speed ✔️ Same allocations ✔️Raw results
|
Throughput/Crank Report ⚡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 (6357) (11.201M) : 0, 11200766
master (10.987M) : 0, 10986728
benchmarks/2.9.0 (11.033M) : 0, 11032866
section Automatic
This PR (6357) (7.190M) : 0, 7190495
master (7.175M) : 0, 7174684
benchmarks/2.9.0 (7.786M) : 0, 7785853
section Trace stats
master (7.577M) : 0, 7577344
section Manual
master (11.201M) : 0, 11201309
section Manual + Automatic
This PR (6357) (6.672M) : 0, 6672490
master (6.769M) : 0, 6769214
section DD_TRACE_ENABLED=0
master (10.257M) : 0, 10257268
gantt
title Throughput Linux arm64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (6357) (9.614M) : 0, 9613923
master (9.557M) : 0, 9557319
benchmarks/2.9.0 (9.495M) : 0, 9494821
section Automatic
This PR (6357) (6.381M) : 0, 6381065
master (6.368M) : 0, 6367805
section Trace stats
master (6.673M) : 0, 6672869
section Manual
master (9.631M) : 0, 9630961
section Manual + Automatic
This PR (6357) (6.014M) : 0, 6014185
master (5.951M) : 0, 5951439
section DD_TRACE_ENABLED=0
master (8.900M) : 0, 8899929
gantt
title Throughput Windows x64 (Total requests)
dateFormat X
axisFormat %s
section Baseline
This PR (6357) (9.826M) : 0, 9825696
master (9.199M) : 0, 9198633
benchmarks/2.9.0 (10.020M) : 0, 10019592
section Automatic
This PR (6357) (6.440M) : 0, 6440086
master (6.083M) : 0, 6082614
benchmarks/2.9.0 (7.255M) : 0, 7255257
section Trace stats
master (6.603M) : 0, 6602631
section Manual
master (9.506M) : 0, 9505886
section Manual + Automatic
This PR (6357) (5.764M) : 0, 5764458
master (5.789M) : 0, 5788592
section DD_TRACE_ENABLED=0
master (8.972M) : 0, 8971897
|
Summary of changes
This should fix the issue
Reason for change
Crashtracker uses
GetThreadDescription
function fromkernel32.dll
(or kernelbase.dll). Which makes this function to be required for loading theDatadog.Profiler.Native.dll
.For some reason, the dynamic loader/linker is unable to find this function. To prevent this, we reuse what's in
OpSysTools
.Implementation details
OpSysTools::GetThreadName
and convert theWSTRING
tostd::string
.Test coverage
Other details
We need to checks that threads are correctly retrieved in crashtracker.