Skip to content

⚡ Bolt: [performance improvement] Pool bytes.Buffer in ResponseWriterWrapper - #384

Open
rschumann wants to merge 1 commit into
mainfrom
bolt-performance-syncpool-3612586863543969662
Open

⚡ Bolt: [performance improvement] Pool bytes.Buffer in ResponseWriterWrapper#384
rschumann wants to merge 1 commit into
mainfrom
bolt-performance-syncpool-3612586863543969662

Conversation

@rschumann

Copy link
Copy Markdown
Contributor

💡 What: Added sync.Pool to recycle bytes.Buffer instances in the ResponseWriterWrapper middleware instead of allocating a new buffer per request. Also ensures the Put action is placed in a defer block in Finalize so early-returned (unlogged) requests don't leak the buffer.
🎯 Why: ResponseWriterWrapper intercepts and records all API request responses. By default, it allocates a new bytes.Buffer for every non-streaming response. This results in heavy allocation pressure on the garbage collector in high-throughput API gateway scenarios. Reusing buffers reduces allocations per operation significantly. To prevent memory leaks, buffers are only returned to the pool if their capacity is <= 128KB.
📊 Impact: Reduces GC pressure and memory allocations per API request.
🔬 Measurement: Benchmark tests show allocations dropping from 14 to 12 per operation, and memory per operation decreasing from ~1200 B/op to ~1088 B/op, improving speed slightly (~1987 ns/op to ~1904 ns/op).


PR created automatically by Jules for task 3612586863543969662 started by @rschumann

Co-authored-by: rschumann <360788+rschumann@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