feat: run scheduled tasks across threads in parallel - #17
Merged
Conversation
Previously, all due tasks executed sequentially in the scheduler loop, meaning one slow task in thread A would block an unrelated task in thread B. Now each due task runs in its own goroutine, with a WaitGroup preventing re-pickup on the next tick. Same-thread serialisation is still enforced by the existing chatState mutex. Adds outboxMu to guard the outbox read+remove cycle against concurrent goroutines sending duplicate file entries.
This file contains hidden or 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
1 participant
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.
Summary
sync.WaitGroup), so tasks targeting different threads run concurrentlychatStatemutex inrunQueuedTaskoutboxMuto prevent concurrent goroutines from reading and sending duplicate outbox entriesTest plan
go build ./...passesgo test ./...passes