Skip to content

Instantly share code, notes, and snippets.

@AngerM
Created October 30, 2018 03:25
Show Gist options
  • Star 25 You must be signed in to star a gist
  • Fork 6 You must be signed in to fork a gist
  • Save AngerM/5059b3ff16292f3fbee990bae7046381 to your computer and use it in GitHub Desktop.
Save AngerM/5059b3ff16292f3fbee990bae7046381 to your computer and use it in GitHub Desktop.
High Performance Golang HTTP Client
package utils
import (
"context"
"io"
"io/ioutil"
"net"
"net/http"
"strings"
"time"
"github.com/rs/dnscache"
)
var Transporter *http.Transport
func init() {
/*
'High performance' http transport for golang
increases MaxIdleConns and conns per host since we expect
to be talking to a lot of other hosts all the time
Also adds a basic in-process dns cache to help
in docker environments since the standard alpine build appears
to have no in container dns cache
*/
r := &dnscache.Resolver{}
Transporter = &http.Transport{
DialContext: func(ctx context.Context, network string, addr string) (conn net.Conn, err error) {
separator := strings.LastIndex(addr, ":")
ips, err := r.LookupHost(ctx, addr[:separator])
if err != nil {
return nil, err
}
for _, ip := range ips {
conn, err = net.Dial(network, ip+addr[separator:])
if err == nil {
break
}
}
return
},
MaxIdleConns: 1024,
MaxConnsPerHost: 100,
IdleConnTimeout: 10 * time.Second,
}
go func() {
clearUnused := true
t := time.NewTicker(5 * time.Minute)
defer t.Stop()
for range t.C {
r.Refresh(clearUnused)
}
}()
}
func getClient(timeout time.Duration) http.Client {
return http.Client{
Transport: Transporter,
Timeout: timeout,
}
}
func buildReq(method, url string, body io.Reader, headers http.Header) (*http.Request, error) {
req, err := http.NewRequest(method, url, body)
if err == nil {
for header, vals := range headers {
for _, val := range vals {
req.Header.Add(header, val)
}
}
}
return req, err
}
/* DoHttpReq:
Wrapper func to use our transport and do a Get or Post request to the other side.
Method is determined by whether you have a body or not
Example:
utils.DoHttpReq("https://www.google.com", 10 * time.Second, nil, nil)
will send a Get request to Google and wait for up to 10 seconds
*/
func DoHttpReq(url string, timeout time.Duration, headers http.Header, body io.Reader) (*http.Response, error) {
method := http.MethodGet
if body != nil {
method = http.MethodPost
}
req, err := buildReq(method, url, body, headers)
if err != nil {
return nil, err
}
c := getClient(timeout)
return c.Do(req)
}
/* DoFireAndForgetHttpReq:
Wrapper func to use our transport and do a Get or Post request to the other side.
Method is determined by whether you have a body or not. This method does the request in
the background and just drops the result
Example:
utils.DoFireAndForgetHttpReq("https://www.google.com", 10 * time.Second, nil, nil)
will send a Get request to Google and wait for up to 10 seconds
*/
func DoFireAndForgetHttpReq(url string, timeout time.Duration, headers http.Header, body io.Reader) {
go func() {
resp, _ := DoHttpReq(url, timeout, headers, body)
if resp != nil {
// Consume the entire body so we can reuse this connection
defer resp.Body.Close()
ioutil.ReadAll(resp.Body)
}
}()
}
@lithdew
Copy link

lithdew commented Feb 24, 2021

Simple 'high performance' http client. In my experience it will end up performing even faster than 'fasthttp' while supporting more features (ex: http2).

'fasthttp' by default enables DNS caching as well; from my experience, fasthttp performs better due to each request requiring a smaller number of heap memory allocations. That being said, it does not support HTTP/2 as you mentioned (though the improvements in speed made by HTTP/2 are somewhat negligible).

@AngerM
Copy link
Author

AngerM commented Feb 24, 2021

'fasthttp' by default enables DNS caching as well; from my experience, fasthttp performs better due to each request requiring a smaller number of heap memory allocations. That being said, it does not support HTTP/2 as you mentioned (though the improvements in speed made by HTTP/2 are somewhat negligible).

Correct, this mirrors most of the 'useful' changes fasthttp does to the standard http client. When we used this at a previous ad-exchange I worked on, we had lower P95 latencies and less CPU over our previous fasthttp based implementation.

@AngerM
Copy link
Author

AngerM commented Jan 6, 2022

Anyone finding this today, there are a few cleanups that should be done similar to: rs/dnscache@06bb552 for better future proofing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment