kgersen
Joined 8 years ago
Joined 8 years ago
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.
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)
The 30% prior isn't the price they're bying at.
it's just that a lot of people think they have to use k8s because it's trendy even it doesn't fit at all their needs and scale. Then they whine it's too complex.
classic PEBCAK issue.
but used a gmail account instead of pro email account (that's not a good move on his part here).
and then he still can't get help from Stadia ?
Possible but very hard to believe.
which "existing western chat and social media" aren't from the US ?
Some countries (like France for instance) impose DNS censorship on ISP to block some domains.