Re: [quicwg/base-drafts] PRIORITY frame on control stream referencing unopened request stream (#2502)

[Patrick Meenan <[e-mail]>]

Serialization within the blocking assets can help quite a bit because the download, parse and eval can be pipelined. If they download in parallel then all of the execution gets batched up after they finished downloading.

"Strict" serialization between blocking and images may not be necessary as long as the ratios are high enough that it is "effectively" serialized. If I recall, the Firefox tree weights the split between groups as 200:100 (for non leader/follower) which isn't enough to pull off effective serialization but it can certainly be done with something like the Firefox tree. If each group could be tagged as round-robin vs serialized it could eliminate the need to build a deeper tree.

Small windows are fine, it's all best-effort anyway otherwise we get HOL blocking. That said, inserting 1 resource per RTT seems like it would be a problem if the RTT's are all serialized. If the cost to boost priority was 1 RTT per resource but they could all be done in parallel it would be fine. Something like a 200-resource page with a 100ms RTT is 20 seconds to prioritize all of them.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2502#issuecomment-491085085