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

v1.18: extends Turbine fanout experiment to wider fanout values (backport of #2373) #2449

Merged
merged 2 commits into from
Sep 10, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 5, 2024

Problem

Based on previous Turbine fanout experiment, larger fanouts are more effective in propagating shreds and reducing repairs: https://discord.com/channels/428295358100013066/478692221441409024/1265782094211321897

However the optimal fanout value cannot be inferred from the experiment.

Summary of Changes

In order to identify optimal fanout value, this commit extends the experiment with wider fanout values.


This is an automatic backport of pull request #2373 done by [Mergify](https://mergify.com).

Based on previous Turbine fanout experiment, wider fanouts are more
effective in propagating shreds and reducing repairs:
https://discord.com/channels/428295358100013066/478692221441409024/1265782094211321897

In order to identify optimal fanout value, this commit extends the
experiment with wider fanout values.

(cherry picked from commit 57144b0)

# Conflicts:
#	sdk/src/feature_set.rs
@mergify mergify bot requested a review from a team as a code owner August 5, 2024 22:57
@mergify mergify bot added the conflicts label Aug 5, 2024
Copy link
Author

mergify bot commented Aug 5, 2024

Cherry-pick of 57144b0 has failed:

On branch mergify/bp/v1.18/pr-2373
Your branch is up to date with 'origin/v1.18'.

You are currently cherry-picking commit 57144b0cea.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   turbine/src/cluster_nodes.rs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   sdk/src/feature_set.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@behzadnouri
Copy link

This is a slight and trivial modification of the experiment currently running on mainnet.
Ideally I would like to get this out asap so that we can settle the optimal turbine fanout before things get more complicated and harder to interpret (e.g. multiple clients, etc).

Copy link

@bw-solana bw-solana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@behzadnouri behzadnouri added the automerge automerge Merge this Pull Request automatically once CI passes label Aug 14, 2024
@mergify mergify bot merged commit 8c42fa8 into v1.18 Sep 10, 2024
37 checks passed
@mergify mergify bot deleted the mergify/bp/v1.18/pr-2373 branch September 10, 2024 14:39
nibty added a commit to FairCrypto/agave-xolana that referenced this pull request Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge automerge Merge this Pull Request automatically once CI passes conflicts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants