Change notify price schedule interval duration from 400ms to 100ms #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the agent code, there are different async actors. There is one actor for getting the prices from the publisher and there is another one to export what is already available to Pythnet/Solana. Some publishers continuously send their updates to agent and they have no problem. However, some publishers wait for a notification from the agent to send their update. The problem with having both at the same frequency is that there is a decent chance that these two intervals don't match with each other and cause occasions on which exporter doesn't have any data or skips one data and it increases the overall latency of our network. This PR changes the notification interval to 100ms to minimize the added latency.