tree 71b623e3085c1d77d53a6189a0658f86a9b5e7ed
parent 062521f3b6f578d2b78f0ba189cf5d7968074cb1
author Duru Can Celasun <dcelasun@apache.org> 1601447151 +0100
committer GitHub <noreply@github.com> 1601447151 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfdCTvCRBK7hj4Ov3rIwAAdHIIADzPmGQOeoQ3dpJ3LiFVvLUI
 rcryupisKuyp6mcrMioJFlEa2CQ7yOaGNjQO6340zBzRF8/F2xvTxxoNIf3jfTYW
 KdwOCzY0QYOo4sCMFAKZGdsU2fMvppLHu1QzZUdpqo9QsbZcFnxmOBicWgVg1J7K
 HBe5MOpT8BIakLuKI8hwhlVxBwF3AVWhaQYNWL6bPcoMGlVwjXlBhSTeMlJ59kd5
 /d/GFWcN6mke01Py61zidK8fZ6ygELgNgKyT2QwJv/8oLDEQFYnEMTCDGut1jxFs
 EnYjJUZOJQf6r5aJC1KBdorTwpq8yqvFxxwuFKf4FnbnviXGe0Q3m6CLbT/ouwo=
 =SF/D
 -----END PGP SIGNATURE-----
 

go: Use sync.Pool for gzip in HTTP transport

b67cad4 introduced transparent gzip support for the HTTP transport but
calling gzip.NewWriter() with every request causes a large number of
memory allocations [1] and can create GC pressure.

Avoid this by using a sync.Pool for gzip writers.

[1] https://old.reddit.com/r/golang/comments/9uejp4/usage_of_syncpool_for_gzipwriter_in_http_handlers/e94jh8c/