Closed kevingosse closed 1 month 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).
Branch report: kevin/string_conversion
Commit report: 4342ed5
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 300432 Passed, 1852 Skipped, 14h 0m 9.27s Total Time
Benchmarks for #5930 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Summary of changes
Fix ToString and ToWString on large strings
Reason for change
Those two methods have a fast-path, where we try to fit the result in a pre-allocated buffer. But when the string is too long, we incorrectly assumed that
WideCharToMultiByte
/MultiByteToWideChar
would return the needed size. In truth, it only does so whencchWideChar
is 0. Because of that mistake, we were returning an empty string.Implementation details
Added a few minor changes while I was at it:
&array[0]
str.data()
instead of&str[0]
Test coverage
Added a unit test for long strings.