-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Experiment with writing a compressed ledger and rsync uncompressed #707
Comments
If the ledger is binary, I am not sure how much compression will offer. Let’s fix the format |
@aeyakovenko Yea, do we have a binary ledger ticket already? This could be more of experiment with ledger format or I can close and add compression as an idea to try to that one. |
i dont think we have one yet. i've been playing around with a 2 file format, one fixed entry size for PoH, the other one for data @rob-solana is looking at it as well |
@sakridge, is this still an issue? |
Obsoleted by #4158 |
Make PPS a parameter instead of the hard coded
Make PPS a parameter instead of the hard coded
Make PPS a parameter instead of the hard coded
…olana-labs#828) Make PPS a parameter instead of the hard coded
…olana-labs#1105) * Parameterize max streams per ms (solana-labs#707) Make PPS a parameter instead of the hard coded Co-authored-by: Lijun Wang <[email protected]>
* Parameterize max streams per ms (#707) Make PPS a parameter instead of the hard coded Co-authored-by: Lijun Wang <[email protected]>
rsync of the ledger with compression requires the leader to compress on-the-fly for each client. In theory writing the ledger compressed to disk may reduce disk IO and also improve rsync speed since it doesn't need to compress on-the-fly.
The text was updated successfully, but these errors were encountered: