⚡ Bolt: Add sync.Pool for ResponseWriterWrapper to reduce allocations - #395
⚡ Bolt: Add sync.Pool for ResponseWriterWrapper to reduce allocations#395rschumann 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: Implemented sync.Pool to recycle
ResponseWriterWrapperobjects during API request logging.🎯 Why: To eliminate repeated memory allocations for this struct on every API gateway request.
📊 Impact: Benchmark results indicate allocations per operation dropped from 5 allocs to 1, and ns/op dropped from ~500 to ~150.
🔬 Measurement: Verify via benchmarking ResponseWriterWrapper creation.
PR created automatically by Jules for task 3584162418113591430 started by @rschumann