β‘ Bolt: Concurrent message processing #13
Merged
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.
π‘ What: Refactored
SatcomForecastCoordinatorto process GPS request messages concurrently instead of sequentially.π― Why: The original implementation processed messages one by one. Since each message involves network I/O (fetching NWS forecast) and SMTP I/O (sending email), sequential processing adds up latency. Parallelizing these operations significantly reduces the total time for a polling cycle when multiple requests are pending.
π Impact: Reduces total processing time roughly to
max(time_per_message)instead ofsum(time_per_message)for a batch of messages.π¬ Measurement: Verify by sending multiple GPS requests to the monitored inbox and observing the logs; processing should start for all messages almost simultaneously. Verified existing tests pass.
PR created automatically by Jules for task 7959835161814093715 started by @clayauld