Re: [go-nuts] a potential problem with go1.11 HTTP library

2018-09-25 Thread Xiangrong Fang
Steven, You are right, I added the domain to my hosts file and the Go client program runs very fast now. The problem is, the domain name in use does exists, and if I ping it, the IP address is resolved instantly! What does this mean in the bug report: DNS queries which are responded to *with

Re: [go-nuts] a potential problem with go1.11 HTTP library

2018-09-25 Thread Steven Hartland
For reference this is the issue tracking the regression I believe your experiencing: https://github.com/golang/go/issues/27525 On 25/09/2018 08:36, Xiangrong Fang wrote: I have a HTTP API and its client written in Go. The client side code is: func upload(link, dir, name string, r io.Reader) {

Re: [go-nuts] a potential problem with go1.11 HTTP library

2018-09-25 Thread Steven Hartland
Sounds like a broken DNS server on the machine, this was something I saw raised before. See the thread "Performance regression of HTTP requests since Go 1.11" for more information.     Regards     Steve On 25/09/2018 08:36, Xiangrong Fang wrote: I have a HTTP API and its client written in Go.

[go-nuts] a potential problem with go1.11 HTTP library

2018-09-25 Thread Xiangrong Fang
I have a HTTP API and its client written in Go. The client side code is: func upload(link, dir, name string, r io.Reader) { var buf bytes.Buffer mw := multipart.NewWriter(&buf) mw.WriteField("dir", dir) mw.WriteField("name", name) ff, _ := mw.CreateFormFile("file", name) io.Copy(ff, r) mw.Close()