Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8370024

HttpClient: QUIC congestion controller doesn't implement pacing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4 P4
    • None
    • 26
    • core-libs

      RFC 9002 [1] states that:

      > Sending multiple packets into the network without any delay between them creates a packet burst that might cause short-term congestion and losses. Senders MUST either use pacing or limit such bursts. Senders SHOULD limit bursts to the initial congestion window; see Section 7.2.

      We don't use pacing, and we don't limit bursts. Bursts happen every time the client resumes sending after an idle period, for example when sending a new request after being idle, or when resuming sending after exhausting the peer's receive window.

      [1] https://www.rfc-editor.org/rfc/rfc9002.html#name-pacing

            djelinski Daniel Jelinski
            djelinski Daniel Jelinski
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: