Optimize DateTime decomposition in CoreLib #1944
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add uses of
DateTime.GetDate(renamed fromGetDatePart) where appropriate.Add internal
DateTime.GetTimemethod to eliminate duplicate computations.Note that the change to
TimeZoneInfo.TransitionTimeToDateTime, which addsTimeOfDaydirectly in ticks precision, can't break anything because theTransitionTimeconstructor ensures thatTimeOfDaydoesn't have sub-millisecond time.Here are the relevant microbenchmarks in dotnet/performance, of which the rows with the bold text being the build with the changes:
System.Tests.Perf_DateTime
System.Tests.Perf_DateTimeOffset
System.Buffers.Text.Tests.Utf8FormatterTests.FormatterDateTimeOffsetNow
System.Text.Json.Tests.Perf_DateTimes