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

Limit final bundle size in B rather than num of blocks #157

Open
segfault-magnet opened this issue Oct 31, 2024 · 0 comments
Open

Limit final bundle size in B rather than num of blocks #157

segfault-magnet opened this issue Oct 31, 2024 · 0 comments
Assignees

Comments

@segfault-magnet
Copy link
Contributor

Rather than having a limit on a number of blocks that can be part of a bundle, we should limit the total acceptable output size of the bundle. This way we have more consistent throughput in times of high traffic on fuel.

Consider changing what we accumulate to be bytes instead of blocks -- i.e. start the bundling process when we have, e.g. 2MB of block data instead of 3600 blocks or 1h passes since the last bundle.

So, we might start configuring the committer to:

Wait for 4MB of block data or 1h, generate bundles only up to 2MB in size (11-12 blobs).

@segfault-magnet segfault-magnet self-assigned this Nov 19, 2024
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

No branches or pull requests

2 participants