nginx process cpu100%

[flx413]

trafficstars

I had a problem using quiche, the nginx worker sometimes be busy, cpu reached 100,the stream always readable in a loop and not exit. the code commit I'm using is 1e9c692c171e8adc819b3c55bf84ceaa06587f1a. Is this problem fixed now? Thanks!

debug log:

2020/12/11 11:24:32 [debug] 29098#29098: quiche: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b rx pkt Short dcid=1de36d4980f7f6fc5034e0c4d4802f21cbe6354b key_phase=false len=1231 pn=3
2020/12/11 11:24:32 [debug] 29098#29098: quiche: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b rx frm NEW_CONNECTION_ID (TODO)   
2020/12/11 11:24:32 [debug] 29098#29098: quiche: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b rx frm STREAM id=0 off=0 len=1173 fin=false
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3::stream: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b read 1 bytes on stream 0
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3::stream: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b read 1 bytes on stream 0
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable
2020/12/11 11:24:32 [debug] 29098#29098: quiche::h3: 1de36d4980f7f6fc5034e0c4d4802f21cbe6354b stream id 0 is readable

[LPardue]

Thanks for the report. That's quite an old commit and we've landed a lot of changes in the meantime that might alleviate this issue. Could you please retry your tests and let us know?

[flx413]

Thanks for your reply.I used ngtcp2 as a client demo.I found that this problem may occur when the client lost packets.I'm looking for more details.

[Ryenum]

Hello, I encountered some problems when configuring the quic service of NGINX. My configuration is the same as that of the official website, but I still cannot use the quic protocol when accessing the server. The h2 protocol is still used. Here is my compilation information: nginx version: nginx/1.16.1 (quiche-83d9168a) built by gcc 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) built with OpenSSL 1.1.1 (compatible; BoringSSL) (running with BoringSSL) TLS SNI support enabled configure arguments: --prefix=/usr/local/nginx --build=quiche-83d9168a --with-http_v3_module --with-http_v2_module --with-quiche=/quiche --with-http_ssl_module --with-openssl=/quiche/quiche/deps/boringssl --add-module=/connect