⚡ Bolt: [performance improvement] Reuse http.Client for API requests - #227
⚡ Bolt: [performance improvement] Reuse http.Client for API requests#227himattm wants to merge 1 commit into
Conversation
Extracted the local http.Client in FetchUsage into a package-level variable to enable connection pooling and TCP keep-alives. Co-authored-by: himattm <6266621+himattm@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
💡 What: Replaced the local
http.Clientinstantiation inFetchUsagewith a package-levelusageHttpClientvariable.🎯 Why: Creating a new
http.Clientfor every request prevents TCP connection reuse (keep-alive) and forces new TLS handshakes, which adds significant latency overhead to API requests.📊 Impact: Decreases latency of repeated API calls by reusing connections. Saves memory and CPU cycles by avoiding repeated TLS handshakes.
🔬 Measurement: Can be measured by benchmarking the time taken for subsequent
FetchUsagecalls; subsequent calls should be significantly faster as they avoid connection setup time.PR created automatically by Jules for task 1498459950166776743 started by @himattm