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

feat: lazily infer max chunk size on write #11

Merged
merged 7 commits into from
Jan 6, 2025

Conversation

tilacog
Copy link
Contributor

@tilacog tilacog commented Dec 30, 2024

Summary of Changes

Lazily compute the max chunk size allowed per WriteMessagePayload instruction, as to optimize the number of required transactions to send the message payload.

Reviewer notes

Just a heads up about the commit history - there are some old commits that'll disappear after squashing. Only the latest commit (d80fc01) matters here. The current diff accurately shows the final changes, though. I probably branched from an outdated version - my mistake on that.

@tilacog tilacog changed the title Relayer/calculate max chunk size on write feat:calculate max chunk size on write Dec 30, 2024
@tilacog tilacog requested a review from eloylp December 30, 2024 19:49
@tilacog tilacog changed the title feat:calculate max chunk size on write feat: dyamilcally calculate max chunk size on write Dec 30, 2024
@tilacog tilacog self-assigned this Dec 30, 2024
roberts-pumpurs
roberts-pumpurs previously approved these changes Jan 6, 2025
@tilacog tilacog changed the title feat: dyamilcally calculate max chunk size on write feat: statically infer max chunk size on write Jan 6, 2025
@tilacog tilacog merged commit 2d0565e into main Jan 6, 2025
6 checks passed
@tilacog tilacog deleted the relayer/calculate-max-chunk-size-on-write branch January 6, 2025 13:07
@tilacog tilacog changed the title feat: statically infer max chunk size on write feat: lazily infer max chunk size on write Jan 6, 2025
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.

4 participants