⚡ Bolt: [performance improvement] Add sync.Pool for response writer buffers - #380
⚡ Bolt: [performance improvement] Add sync.Pool for response writer buffers#380rschumann wants to merge 1 commit into
Conversation
Co-authored-by: rschumann <360788+rschumann@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. |
💡 What: Added
sync.Poolto reusebytes.BufferinResponseWriterWrapper.🎯 Why: Every API request was allocating a new
bytes.Bufferto capture the response body for logging, causing unnecessary GC pressure and memory allocations in the hot path.📊 Impact: Significantly reduces per-request allocations for the API gateway.
🔬 Measurement: Go benchmarks show reduced memory allocations when initializing and using the response writer wrapper.
PR created automatically by Jules for task 6709427601771959753 started by @rschumann