search

netty / netty-incubator-codec-quic

Apache License 2.0
301 stars 70 forks source link

quicSreamChannel isWritable often return false #650

Closed chendali16 closed 8 months ago

chendali16 commented 9 months ago

When using quic for data transmission, the server uses QuicStreamChannel to write data. The channel isWritable is often false. How can I adjust the channel parameters to improve the throughput of writing data?

normanmaurer commented 8 months ago

This means that the remote peer did not give you "credits" back. There is not much you can do here as its how the remote peer does it back-pressure

normanmaurer commented 8 months ago

English please

chendali16 commented 8 months ago

This means that the remote peer did not give you "credits" back. There is not much you can do here as its how the remote peer does it back-pressure

With the same processing logic for both the server and client, when I use the KCP protocol for transmission, the tps is more than 10 times larger than that of Quic. KCP has better transmission performance than Quic, but the difference cannot be so large？ Is this due to other conditions, such as buffer size and buffer queue