Uh oh!
There was an error while loading. Please reload this page.
Add Perf_String_Substring_* benchmarks - #2178
Conversation
| [Arguments("dzsdzsDDZSDZSDZSddsz", 0)] | ||
| [Arguments("dzsdzsDDZSDZSDZSddsz", 7)] | ||
| [Arguments("dzsdzsDDZSDZSDZSddsz", 10)] | ||
| [Arguments("dzsdzsDDZSDZSDZSddsz", 19)] |
There was a problem hiding this comment.
probably will delete this change, so ignore it
| // public void Substring_Full() => "abc".Substring(0, 3); | ||
| // [Benchmark] | ||
| // public void Substring_Empty() => "abc".Substring(0, 0); |
There was a problem hiding this comment.
not sure these are of any interest but they showed that with the new changes the JIT can fully compile away substring code compared to before
nietras
commented
Dec 10, 2021
build errors |
danmoseley
commented
Dec 10, 2021
Not sure why those build failures don't show up when I build locally. There should be something like this suppressing them though. |
nietras
commented
Dec 11, 2021
Suppressed the warning in the places this was missing. See PR. Then getting assets issue: so switched to |
nietras
commented
Dec 14, 2021
Reported some results in dotnet/runtime#62577 (comment) |
danmoseley
commented
Feb 5, 2022
@nietras checking in on this one, do you believe it's ready to review (after resolving conflicts)? |
a668e00 to
6e1617cComparedanmoseley
commented
Feb 8, 2022
@nietras I'm closing this one as it seems that string.Substring(int) and string.Substring(int, int) are already covered very similarly. Please let me know if that's not the case. |
Draft benchmarks for Substring. cc @adamsitnik feel free to make any changes you like right away. For some reason I can no longer built this after updating latest main. In relation to dotnet/runtime#62577