Opened 4 months ago

Last modified 5 weeks ago

#2621 new defect

QUIC ACKs could be delayed by congestion controllers

Reported by: yangfurong@… Owned by:
Priority: minor Milestone:
Component: other Version: 1.23.x
Keywords: quic, ack Cc:
uname -a: 4.19.91-013.xxxxx.xxxxx.x86_64
nginx -V: nginx/1.23.0


In NGINX QUIC, all QUIC ACK frames have to go through the congestion window limitation. This is problematic, as ACK frames could be delayed too much (even exceeding the max_ack_delay). As a consequence, the peer communicating with NGINX could see prolonged RTTs and may not be able to timely increase its congestion window.

Ideally, the ACK returning logic should be:

  1. If there is free space in the congestion window and there are other frames going to be sent, ACK frames could be bundled with these frames and sent out together;
  2. If the max_ack_delay has been reached, ACK frames must be sent immediately no matter whether there is available cwnd or not (pure ACK packets should be sent if there is no available cwnd).

Attachments (1)

quic-ack-cwnd (3.7 KB ) - added by Roman Arutyunyan 4 months ago.

Download all attachments as: .zip

Change History (4)

comment:1 by Roman Arutyunyan, 4 months ago

Thanks for reporting this. I see two potential benefits from this improvement. The first one is resolving a potential temporary deadlock when both peers are waiting for ACKs and both congestion windows are exhausted. The second one is a performance improvement while operating normally. We are currently evaluating a solution.

by Roman Arutyunyan, 4 months ago

Attachment: quic-ack-cwnd added

comment:2 by Roman Arutyunyan, 4 months ago

The attached patch should fix the issue. However we haven't seen any performance improvements under normal conditions. The evaluation is still ongoing.

comment:3 by yangfurong@…, 5 weeks ago

This patch could generate a pure ACK pkt for every incoming ack-eliciting packet when there is no available cwnd. In ngx_quic_generate_ack, it only delays ACK if the send queue is empty (

Note: See TracTickets for help on using tickets.