Skip to content

⚡ Bolt: Use connection pooling for concurrent Supabase storage uploads#47

Open
kourdroid wants to merge 1 commit into
mainfrom
bolt-optimization-supabase-storage-pooling-3448507274474855146
Open

⚡ Bolt: Use connection pooling for concurrent Supabase storage uploads#47
kourdroid wants to merge 1 commit into
mainfrom
bolt-optimization-supabase-storage-pooling-3448507274474855146

Conversation

@kourdroid

Copy link
Copy Markdown
Owner

💡 What: Implemented __aenter__ and __aexit__ in SupabaseStorage to support acting as an asynchronous context manager, sharing a single httpx.AsyncClient across sequential/concurrent upload requests. Updated the /ingest route to wrap storage upload logic inside an async with block, and updated relevant test mocks to behave correctly as context managers.

🎯 Why: Previously, during PDF splitting in the /ingest route, the system instantiated a new SupabaseStorage client, but the underlying HTTP client (httpx.AsyncClient) was instantiated inside the upload method on every call. This meant that each concurrent upload (even though batched using asyncio.gather) was opening a brand new TCP connection and performing a full TLS handshake, causing a severe N+1 latency bottleneck.

📊 Impact: Reduces storage upload connection overhead from O(N) to O(1) by reusing a single HTTP client connection pool across all uploaded split chunks.

🔬 Measurement: Verify by running pytest tests/test_api_ingest.py and reviewing logs for the /ingest endpoint to ensure uploads still succeed but execute significantly faster under load.


PR created automatically by Jules for task 3448507274474855146 started by @kourdroid

Co-authored-by: kourdroid <36898160+kourdroid@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