[rgbrenner]

Your experience with http 1.1 to origin matches mine. I'm not suggesting using http 1.1 from edge > origin. Most CDNs are currently doing that, and it doesn't perform well.

I should be more specific in my description: We are using http2 everywhere.

There's a single http2 connection between the client and edge (the customer could setup sharding, but there's no way for us to force it).

That edge node has a pool of http2 connections to other PoPs, and maintains QoS stats for each PoP. It'll pick the fastest path to send the request. The pool is large enough to service all of the requests that are being handled at any one time. So in effect, if the client sends 10 requests to the edge node, each of those will be sent edge<->edge over 10 http2 connections. (The connections in the pool are kept active, so there's no tls resumption delay either.)

Once the edge node near the origin has received it, there's a smaller http2 pool to the origin server.

So at the origin, it's handling a handful of requests in parallel.. even if there's only a single client making all of the requests.

I think that's a bit clearer.. I've been happy with the performance we're getting from this.. but plan to test sctp and quic later this year for edge<->edge.

[nocarrier]

Ah cool, that's similar to what we did. I think http2 gets a bad rap, we saw a lot more positives than negatives from it. You should do a writeup after you test sctp and quic, I'd be pretty interested in reading it and I bet others would too.