ix.netcom.com wrote:
>
> Use the replace directive to point the net package to your local copy.
>
> Much easier to test X changes than stdlib changes.
>
> On Nov 19, 2021, at 10:58 AM, Kirth Gersen wrote:
>
> Your CL works well with the POC.
>
>
> Side questio
sing that transport,
>>>> so it is probably better to create a transport specifically for the
>>>> high-throughput transfers.
>>>>
>>>> You can also create perform single shot requests like:
>>>>
>>>> if useH2C {
>>>>
i'm trying to use http client to connect in http/2 clear text (H2C).
this works:
var dialer = &net.Dialer{
Timeout: 5 * time.Second, // fail quick
FallbackDelay: -1, // don't use Happy Eyeballs
}
rt = &http2.Transport{
AllowHTTP: true,
DialTLS: func(network, addr string, cfg *tls.Config) (net.Con
er to achieve maximum performance.
>
> So 38Gbps for http2 vs 55 Gbps for http1. Better but still not great.
> Still, with some minor changes, the net package could allow setting of a
> large frame size on a per stream basis - which would enable much higher
> throughput. The gRPC
http/2 implementation seems ~5x slower in bytes per seconds (when transfer
is cpu capped).
POC: https://github.com/nspeed-app/http2issue
I submitted an issue about this 3 months ago in the Go Github (
https://github.com/golang/go/issues/47840 ) but first commenter
misunderstood it and it got b
