-
Notifications
You must be signed in to change notification settings - Fork 127
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
Geyser stream of full blocks is lagging/falling behind #307
Comments
the effect is also dependent on the downstream network link speed |
found that this configuration changes in the GrpcClient helps:
related - there is a documentation issue with h2/hyper regarding these parameters (issue) |
Are you able to process the stream quick enough? Do you have any kind of bandwidth limitation downstream? |
the strange thing is that Data gets soaked into black hole. wonder how grpc service could spot that issue. |
@grooviegermanikus can you please try version 1.14.1? PRs #313 & #315 should improve performance |
Problem
The full block stream cannot keep up with slot progression on the chain and also not with block meta sent via geyser.
Lag is approx 42 slots in 60 seconds (mainnet)!
Did not observe that lag on testnet.
The text was updated successfully, but these errors were encountered: