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

Different request limits for request type in chain download #7694

Open
jframe opened this issue Oct 1, 2024 · 0 comments
Open

Different request limits for request type in chain download #7694

jframe opened this issue Oct 1, 2024 · 0 comments
Labels
P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) syncing

Comments

@jframe
Copy link
Contributor

jframe commented Oct 1, 2024

Different request limits for request type in chain download. The size of each type varies quite significantly e.g. block body sizes are much larger than headers or receipts. By changing the request limit per type we could have more consistent downloading in the pipelines. Requesting a large number of entries can result in timeouts or the peers returning less data.

@jframe jframe added the syncing label Oct 1, 2024
@jflo jflo added P4 Low (ex: Node doesn't start up when the configuration file has unexpected "end-of-line" character) P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) and removed P4 Low (ex: Node doesn't start up when the configuration file has unexpected "end-of-line" character) labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) syncing
Projects
None yet
Development

No branches or pull requests

2 participants