3 ms·
I was just talking about DNS not this other stuff. But now that you bring it up, isn't the 6 resources per domain outdated? At least for HTTP2? When I've done
by weird-eye-issue 4y ago
I was just talking about DNS not this other stuff.
But now that you bring it up, isn't the 6 resources per domain outdated? At least for HTTP2? When I've done performance testing on my site lately it definitely seemed to load more than 6 resources in parallel from one domain but I haven't looked into this topic in a long time (back when it definitely was limited)
- deleted 4y ago[deleted]
- littlecranky67 4y agoYes, I was explicitly referring to HTTP1/1. With HTTP2, connection multiplexing is baked into the HTTP/2 protocol. But again, whether or not this speeds things is hard to tell without knowing all relevant parameters. There is a reason HTTP/3 uses QUIC over UDP, the main motivation was to put the userspace (i.e. browser) more in control over congestion control and such things (while TCP is always kernel-implementation dependent). And I think we will see lot of different implementations and innovations in this field (just as there is a ton of different TCP congestion window scaling algorithms).