Optimize sum of Durations by using custom function #51598
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.
The current
impl Sum for Duration
usesfold
to perform severaladd
s (or reallychecked_add
s) of durations. In doing so, it has to guarantee the number of nanoseconds is valid after every addition. If you squeese the current implementation into a single function it looks kind of like this:We only need to check if
nanos
is in the correct range when giving our final answer so we can have a more optimized version like so:We now only convert
total_nanos
tototal_secs
(1) iftotal_nanos
overflows and (2) at the end of the function when we have to output a validDuration
. This gave a 5-22% performance improvement when I benchmarked it, depending on how big thenano
value of theDuration
s initer
were.