Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perf(cu): use cached readState on dryRun if within allowed max age #984 #1009

Merged
merged 2 commits into from
Sep 10, 2024

Conversation

TillaTheHun0
Copy link
Member

@TillaTheHun0 TillaTheHun0 commented Sep 9, 2024

Closes #984

This also adds an optimization downstream from chaining evaluation streams: if there is overlap between chained eval streams, which can happen if many messages are sent a process and requested from the CU close together (the result calls may arrive out of order to the CU), then the CU will more likely serve that overlap from the evaluation cache rather than spin up another evaluation stream. This should help reduce resource contention for messages that have already been evaluated.

The majority of the diff in dryRun is just rejigging the Async chain to be more declarative. There is a bit more going on in the steps and it's more kosher to use a declarative style, so that the intent is not lost in the implementation details.

@TillaTheHun0 TillaTheHun0 merged commit f3acc36 into main Sep 10, 2024
3 checks passed
@TillaTheHun0 TillaTheHun0 deleted the tillathehun0/cu-dry-run-cache branch September 10, 2024 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat(cu): utilize cache on dry-run if underlying state was recently evaluated.
1 participant