Skip to content

⚡ Bolt: Prevent event loop blocking in async routes - #96

Open
benpiper wants to merge 1 commit into
mainfrom
bolt-async-threadpool-8965965160403963842
Open

⚡ Bolt: Prevent event loop blocking in async routes#96
benpiper wants to merge 1 commit into
mainfrom
bolt-async-threadpool-8965965160403963842

Conversation

@benpiper

@benpiper benpiper commented Jul 5, 2026

Copy link
Copy Markdown
Owner

💡 What: Wrapped CPU-bound bcrypt hashing/verification functions (get_password_hash and verify_password) in backend/auth.py with starlette.concurrency.run_in_threadpool, making them asynchronous, and updated all callers in backend/main.py and backend/auth.py to await them. Also replaced a synchronous time.sleep(1) loop in get_frame_image with await asyncio.sleep(1).
🎯 Why: In FastAPI, running CPU-bound operations (like bcrypt) or synchronous blocking calls (time.sleep) directly inside async def routes blocks the entire event loop. This starves the server and prevents it from handling concurrent requests effectively.
📊 Impact: Significantly improves server concurrency and responsiveness, eliminating bottlenecks during user authentication and image polling.
🔬 Measurement: Verified functionality by passing all existing backend tests (pytest tests/). Performance improvements can be measured under load testing by observing the API's concurrent request handling capabilities.


PR created automatically by Jules for task 8965965160403963842 started by @benpiper

Co-authored-by: benpiper <4343814+benpiper@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant