Skip to content

Conversation

@emwang-jump
Copy link
Contributor

No description provided.

@emwang-jump emwang-jump changed the title some fix32 shred: assume fixed-32 fec sets Dec 30, 2025
@emwang-jump emwang-jump marked this pull request as ready for review December 30, 2025 17:31
@github-actions
Copy link

Performance Measurements ⏳

Suite Baseline New Change
backtest mainnet-368528500-perf per slot 0.05061 s 0.050573 s -0.073%
backtest mainnet-368528500-perf snapshot load 1.633 s 1.642 s 0.551%
backtest mainnet-368528500-perf total elapsed 50.609558 s 50.573484 s -0.071%
firedancer mem usage with mainnet.toml 1005.23 GiB 1005.23 GiB 0.000%

@github-actions
Copy link

Performance Measurements ⏳

Suite Baseline New Change
backtest mainnet-368528500-perf per slot 0.050643 s 0.050655 s 0.024%
backtest mainnet-368528500-perf snapshot load 1.713 s 1.699 s -0.817%
backtest mainnet-368528500-perf total elapsed 50.642606 s 50.655248 s 0.025%
firedancer mem usage with mainnet.toml 1005.23 GiB 1005.23 GiB 0.000%

@ptaffet-jump
Copy link
Contributor

Is there a reason to keep the shred34 struct? I think we should get rid of it, and simplify the structures

@emwang-jump
Copy link
Contributor Author

Is there a reason to keep the shred34 struct? I think we should get rid of it, and simplify the structures

No good reason, just haven't gotten to it yet!

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.

3 participants