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

Up network buffers to 64MB max #1057

Merged
merged 1 commit into from
Aug 25, 2018

Conversation

sakridge
Copy link
Member

500ms of data at 1Gbps = 125GB/2 = 64MB
Seems to help tx rate in GCP network tests.

500ms of data at 1Gbps = 125GB/2 = 64MB
Seems to help tx rate in GCP network tests.
@sakridge sakridge merged commit c641ba1 into solana-labs:master Aug 25, 2018
@sakridge sakridge deleted the up-network-buffer-size branch August 25, 2018 01:17
CriesofCarrots pushed a commit to CriesofCarrots/solana that referenced this pull request May 3, 2024
Looking up Merkle root of the last erasure batch for the parent block
can fail if the slot-meta is not yet available in blockstore.
This commit instead retains chained Merkle root across leader slots. If
the parent of the current block is the previous leader slot, then the
chained Merkle root is readily available and we can bypass blockstore
lookup.
willhickey pushed a commit that referenced this pull request Jun 8, 2024
…1057) (#1182)

retains chained Merkle root across leader slots (#1057)

Looking up Merkle root of the last erasure batch for the parent block
can fail if the slot-meta is not yet available in blockstore.
This commit instead retains chained Merkle root across leader slots. If
the parent of the current block is the previous leader slot, then the
chained Merkle root is readily available and we can bypass blockstore
lookup.

(cherry picked from commit 6b45dc9)

Co-authored-by: behzad nouri <[email protected]>
ryoqun pushed a commit to ryoqun/solana that referenced this pull request Jun 10, 2024
…olana-labs#1057) (solana-labs#1182)

retains chained Merkle root across leader slots (solana-labs#1057)

Looking up Merkle root of the last erasure batch for the parent block
can fail if the slot-meta is not yet available in blockstore.
This commit instead retains chained Merkle root across leader slots. If
the parent of the current block is the previous leader slot, then the
chained Merkle root is readily available and we can bypass blockstore
lookup.

(cherry picked from commit 6b45dc9)

Co-authored-by: behzad nouri <[email protected]>
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.

1 participant