kgersen · HackerTrans

3 lata temudiscuss

I moved to Tailscale, until I find something simpler, I'm not moving back.

4 lata temudiscuss

thx i'll look at v2.6.

4 lata temudiscuss

We do speed tests hence we saw the issue. See https://github.com/golang/go/issues/47840

Yeah I agree this is a edge case, 99,99% of Caddy users don't push so much data ;)

But Caddy can't be used as a big files download server for instance, unless sticking with HTTP/1.1 (that and sendfile + kTLS not been supported last time I checked?) (at least with a single http instance).

Another issue for HTTP/3 is https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-B... Current Linux in WSL for instance has this issue. This will probably resolves over time as more and more Linux distros will take HTTP/3 requirements into account.

kgersen

4 lata temudiscuss

Beware of a performance hit (in term of bps not req/s) if you push big data with Caddy.

Go implementation of HTTP/2 already took a /5 hit over http/1.1 (Go http/2 implementation is 5x slower than Go http/1.1)

With HTTP/3 our early benchs indicate /2 ot /3 from HTTP/2 (so /10 from http/1.1)

kgersen

4 lata temudiscuss

I don't see any discount. They're bying at $95 per share. Look at YTD and 5Y prices.

The 30% prior isn't the price they're bying at.

kgersen

5 lat temudiscuss

A Go project is easy to contribute to. That's a huge factor for an open source project.

comments