While it might not be the initial problem, you're creating a new proxy and a new http.Transport on every request. At the end of that request that transport will probably still contain the open connection which you can no longer use. That's going to tie up the FD until the keepalive can kill it, which IIRC how Go sets the options in linux is going to be 10min with the 30s interval you're setting.
You always want to reuse http.Transports. On Wednesday, November 16, 2016 at 12:01:50 AM UTC-5, Tom wrote: > > Hi guys, > > I've been working on a HTTP reverse proxy that has an auth/authorization > function. It all works well, however I have noticed significant additional > latency - and I cannot work out why. From what I can tell, me hitting my > service from chrome on localhost should work just fine - I have a very > beefy machine! (8core 3.4Ghz Amd64) > > Anyone have any insights into httputil.ReverseProxy, or have any ideas > where to begin? > > The method is here: > https://github.com/twitchyliquid64/pushtart/blob/master/src/pushtart/webproxy/handler.go#L61 > > Cheers, > Tom > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
