-
Notifications
You must be signed in to change notification settings - Fork 691
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
Node: Observation batching #3977
Node: Observation batching #3977
Conversation
4e6c95b
to
fd94f23
Compare
be3eceb
to
a3a513a
Compare
4ca598b
to
2bf941c
Compare
A concern has been raised regarding possible latency impacts of this change. Therefore I am converting this PR back to draft until those concerns can be addressed. |
The availability of Pyth's market data with as little latency as possible is a very strong usecase to warrant not being part of observation batching, and so they should be excluded from it. |
9e3524a
to
dcd325e
Compare
81554ba
to
601ffc8
Compare
This PR is being superseded by PR #4066, so this one is being closed. |
This PR introduces the batching of observations by adding the
SignedObservationBatch
gossip message. It modifies the guardian to wait up to one second in order to batch as many observations as possible (up to 4000) into a single gossip message. This not only reduces gossip traffic but also the load on the guardians and applications that listen to observations.This PR is meant to go hand-in-hand with PR #4000, which further improves gossip traffic by splitting it across different topics, allowing the guardians and gossip listeners (like spies and flies) to only subscribe to the topics they need.
NOTE: Once the gossip network cutover is complete, support for
SignedObservation
(individual observation) messages will be dropped, but in the meantime, applications that listen to observations need to support both message streams.