Don't schedule response HEADERS with priority tree
Previously we scheduled the transmission of response HEADERS using priority tree in the belief that it allows more better utilization of bandwidth for prioritized streams. But to reduce the overhead of reconstruction of priority queue when connection level flow control window is depleted, we just don't check priority tree in this case. This means that response HEADERS frames are not sent even though they are not flow controlled. This could waste bandwidth. To improve this situation, we stop scheduling response HEADERS with priority tree for now. Now they are just sent in the order they submitted. The response body DATA continued to be scheduled with priority tree as before.
Showing
Please register or sign in to comment