perf: fix false parallelism — sequential awaits disguised as concurrent #87
Labels
No Label
ai-changes-requested
ai-pr-opened
ai-reviewed
ai-reviewing
ai-working
in-next-release
status/in-progress
status/pr-open
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/major-domo-v2#87
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Several places create coroutine objects and then
awaitthem sequentially, which looks like parallelism but executes serially. In Python,coro = some_async_func()does NOT start execution — it only begins onawait.Locations
commands/transactions/management.pylines 137–143services/stats_service.pylines 132–163 (get_player_stats)Fix
Replace with
asyncio.gather():Impact
HIGH — These are user-facing commands where each API call adds 50–200ms of latency that could overlap.