-
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
Subscribe Very Slow / Hanging [Rust & Python] #489
Comments
What's the latency between producer and consumer? do you have enough bandwith for your filters? |
@Juanito87 thanks for the reply. Both producer and consumer are on the same machine if that's what you mean. Client is pointing to 127.0.0.1. As far as Using the rust client my request looks just like this Using Python my request looks like this:
|
@Juanito87 I have been able to get some data to stream but not consistently. The machine I am using now has 64 cores and 512 GB of ram. The cores are AMD 2.5GZ boosting to 3.0GZ. Local NVME drives stripped and separate drives for accounts and the ledger. I am having the same issues with Websockets, the Rust client, and Python. Seems like others are running with these configs just fine. I just don't know what the issue could be. My agave-validator config looks like this:
And my Yellowstone config looks like this:
|
Subscribing to a stream is very very to return a result. Sometimes it will return in 45 seconds and sometimes it returns nothing after 3 hours. I'm running Solana 2.0.18 and Yellowstone v3.0.1+solana.2.0.18.
How fast should blocks be returned and what could be causing such a significant delay?
Example can run for hours and return nothing:
Responses not requiring a subscription return instantly:
Yellowstone Config:
The text was updated successfully, but these errors were encountered: