PubSub controller changes #1596
Assignees
Comments
Open
Merged
matt2e
added a commit
that referenced
this issue
Jun 6, 2024
closes #1596 closes #1642 How it works: - pubsub managers poll for subscriptions that are behind the topic's head - locks these subscriptions for the tx - skips subscriptions that are already locked - Then finds the next event for each subscription - If the event is newer than our artificial delay, we skip this subscription on this attempt Pubsub also speeds things up by: - Polling once a second - When it schedules an async call, notifies controller so we can attempt to pick it up straight away - this is wrapped in a mutex so that we don't accidentally get more and more async calls running at once on a single controller - When the async call is completed, pubsub is notified so that it can immediately try progressing subscriptions again
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: