🚀 Performance Improvement: Parallelize Session Cleanup with asyncio.gather() #1649
+270
−77
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
This PR optimizes session cleanup in SessionRegistry by parallelizing database refresh operations using asyncio.gather() instead of executing them sequentially. The change eliminates O(n) cleanup behavior and significantly reduces cleanup latency under high session counts.
❌ Problem
The existing session cleanup logic executed asyncio.to_thread() calls sequentially inside a loop:
With 100 sessions and ~50ms DB latency per session:
✅ Solution
📈 Performance Results
Test output:
Actual parallel cleanup time: 0.438 seconds
Speedup: 11.4x faster than sequential
✅ PASS: Parallel cleanup is significantly faster
🧪 Testing
Run