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

Investigate the effiency of the chain download pipeline #7696

Open
jframe opened this issue Oct 1, 2024 · 1 comment
Open

Investigate the effiency of the chain download pipeline #7696

jframe opened this issue Oct 1, 2024 · 1 comment
Assignees
Labels
P2 High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc)) syncing

Comments

@jframe
Copy link
Contributor

jframe commented Oct 1, 2024

Investigate the efficiency of the chain download pipeline. There could be some pauses in the pipeline due to waiting on stages to complete.

@jframe jframe added the syncing label Oct 1, 2024
@jflo jflo added the P2 High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc)) label Oct 8, 2024
@ahamlat
Copy link
Contributor

ahamlat commented Oct 8, 2024

Yes, agreed. The pipeline is a set of steps that are executing in parallel and in a certain order. Each stage is dependant from the stage before and the stage after as we can see in the diagram below. We need to review the metrics to be able to spot wait time on each step on either when putting data to the next step or when reading data from the step before.
In a perfect configuration, each step should be doing work all the time, not blocking on either the step before or the step after.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc)) syncing
Projects
None yet
Development

No branches or pull requests

4 participants