Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Re-design processor/coordinator interactions #565

Open
kayabaNerve opened this issue Apr 26, 2024 · 2 comments
Open

Re-design processor/coordinator interactions #565

kayabaNerve opened this issue Apr 26, 2024 · 2 comments
Labels
coordinator feature New feature or request processor

Comments

@kayabaNerve
Copy link
Member

The current message queue is an interactive ordered process not amenable to rebuilding one but not both.

Interactions should be designed as an append-only series of data blobs queriable at any time in a way either can successfully be rebuilt. This would also parallelize the ordering, improving performance and preventing the risk of deadlocks.
@kayabaNerve
Copy link
Member Author

I'm unsure we can get to this prior to mainnet :///

This was referenced May 7, 2024
Closed
Closed
@kayabaNerve
Copy link
Member Author

processor-smash is premised on reading from the message-queue, then internally dispatching without locks/blocking yet queueing. It accordingly doesn't mean this issue would improve performance, and has already resolved the deadlock concerns.

The ability to rebuild remains its own active question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
coordinator feature New feature or request processor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kayabaNerve