-
Notifications
You must be signed in to change notification settings - Fork 205
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
getHeader and submitBlindBlock latencies #203
Comments
That's great, thank you for reporting. Well investigate today and update here. |
We've updated our Relay and builder infrastructure across all the supported testnets (Kiln, Ropsten and Sepolia), and we're seeing very quick response timings now (in the single-digit milliseconds mostly). Also it's not necessary anymore to batch validator registrations in small chunks, you can many registrations with a single call without problems. Let us know if you can confirm the numbers from your end, or if we need to further investigate network delays. |
@tbenr @terencechain do you have any current charts for the last days/week? |
Not sure if this is the best place to track this. Feel free to close this and let me know a more appropriate place, we can move the issue somewhere else.
I've been observing high latencies with both getStatus, getHeader and submitBlindBlock calls using the Kiln relay.
getStatus, between 100-500ms
getHeader, this gotten worse in the last 24 hours, many calls exceeded 1-2s
submitBlindBlock, mostly around 200ms
This is a prysm beacon node getting a beacon block for validator to sign. We are seeing 10-25x latency increases
I understand that many moving parts are currently under optimized, but I still want to open an issue for tracking
The text was updated successfully, but these errors were encountered: