-
Notifications
You must be signed in to change notification settings - Fork 7
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
Investigate message format optimisation #757
Milestone
Comments
Based on 10k message samples collected from Compressing messages is therefore worthwhile indeed. |
masih
added a commit
that referenced
this issue
Dec 11, 2024
Modify observer to report space gain by compressing GPBFT messages using zstd. Add a compression test that measures space gain in compressing generated finality certificates. The results run on `filecoin/46` passive testing show that compressing GPBFT messages gain ~60% in space saving. The latest captured so far: ``` messages observed so far: 37648 Min compression gain: 7.4 % Max compression gain: 69.0 % Avg compression gain: 57.3 % ``` Relates to: #757
Also see: #792 |
rjan90
modified the milestones:
Milestone 5: important optimization post activation,
Milestone 2.5: Mainnet Deployment Readiness
Dec 13, 2024
BigLep
modified the milestones:
Milestone 2.5: Mainnet Activation,
Milestone 2: Mainnet Passive Testing
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The message format optimisation currently has a number of low hanging fruits:
Of the ones above, compression seems to be the most straightforward one to try.
The text was updated successfully, but these errors were encountered: