feat: bump max EigenDA batch size to 16mib #36
Merged
Conversation
This file contains 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
bxue-l2
reviewed
Oct 7, 2024
…riggered manually
epociask
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
MaxEigenDABatchSizeto 16 MBmaxDecompressionLento 40 mib. This constraint was causing the batch poster to detect overflows and limit the batches to 5-7mb post-compression using a constant ratio of 4. Increasing it resulted in batches around exactly 16MB post compression.Testing
Tests were conducted against a testnode environment on an EC2 using EigenDA Holesky. Under higher load (i.e, 90 Kb/s) and reduced EigenDA bridge intervals (i.e, 3 minutes), the chain was able to maintain liveness with the latest->confirmed message diff being constant over multiple hours of load.