feat: Only initialize BusinessCalendar caches when data is accessed and improve caching performance#5378
Merged
chipkent merged 57 commits intodeephaven:mainfrom Oct 23, 2024
Merged
Conversation
… improving caching.
jjbrosnan
reviewed
Apr 19, 2024
Contributor
jjbrosnan
left a comment
There was a problem hiding this comment.
I don't have any specific comments on the code. I was unable to break things when testing this locally. I tested against docs CI, and ran my own tests locally with no issues.
devinrsmith
reviewed
Jun 18, 2024
rcaudy
reviewed
Sep 24, 2024
rcaudy
reviewed
Oct 23, 2024
Minimizing the lifetime of recomputed values.
rcaudy
approved these changes
Oct 23, 2024
Member
rcaudy
left a comment
There was a problem hiding this comment.
Reviewed enough, has great test coverage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Makes BusinessCalendar caches populate only when accessed to avoid slow worker initialization. Additionally, caching in various operations has been improved to yield better performance.
Resolves #5377
Benchmark:
Performance:
Note1:
v0.33.0times do not include initialization times, but the new values do.Note2: There appears to be contention or initialization overhead in the partitioned table case yielding slightly worse performance.