proposal: net/http: make buffer size or buffer pool in copyBufPool configurable

[Keynib]

Proposal Details

The net/http/server.go implementation uses an internal, unexported buffer pool with a fixed size (copyBufPoolSize = 32 * 1024). This value is hard-coded and cannot be adjusted or replaced by users.

For some workloads, especially high-throughput reverse proxies or systems working with large payloads, the default buffer size may be suboptimal. It would be beneficial to allow customizing this behavior. The bigger buffer size allows reducing the amount number of system calls and improve performance.

I think some kind of ReverseProxy Buffer Pool may be used here.

Linked issues

#57202

[gabyhelp]

Related Issues

• proposal: net/http: a configurable write buffer size for the http server #68149 (closed)
• proposal: net/http: configurable Server.WriteBufferSize #13870
• net/http: consider adding configurable buffer sizes to Transport #22618 (closed)
• net/http: make ResponseWriter buffer size configurable #7467 (closed)
• net/http: consider reusing buffers replacing io.Copy calls with io.CopyBuffer #12455 (closed)
• net/http: use copyBufPool in transferWriter.doBodyCopy() #57205 (closed)
• net/http: make the http server con write buffer size configurable #68142 (closed)
• net/http: implementing size capped connection pools #12289 (closed)
• x/net/websocket: Ability to reuse read/write buffers between connections. #18048 (closed)

Related Discussions

• net/http: newBufioWriterSize in newConn

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[seankhliao]

do you have benchmarks that show the scale of the improvement?

[Keynib]

@seankhliao Hello! I've tested one more time the idea on my projects, and the increasing of copyBufPoolSize doesnt provide any performance benefits.

So, there is no need to change something for now, I close the issue. Thank you for you time, if I find something new related to described problem, I will add information here.