You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using quic Netty, which uses QUICHE QUIC.
And I noticed that when there are too much traffic, the idle connection is being triggered, even though the receivers did not receive all the data sent by the sender. And when I increase the idle timeout value, the receivers receive all the data but much later.
Have you ever faced an issue like this ?
The experiment consists in a QUCI Netty server application sending 1GB file to 6 NETTY QUIC clients. I am running the experiments
in two identical servers with high network connectivity. In one I run the server application plus 3 clients, and on the other I run the rest of the clients (3 clients).
And these are the technical description of the servers:
processor: 2 x AMD EPYC 7343 | cpu cores/threads: 32⁄64 | RAM: 128 GiB DDR4 3200 MHz | network interfaces: 2x10 Gbps | 450 GB SSD
The text was updated successfully, but these errors were encountered:
I am using quic Netty, which uses QUICHE QUIC.
And I noticed that when there are too much traffic, the idle connection is being triggered, even though the receivers did not receive all the data sent by the sender. And when I increase the idle timeout value, the receivers receive all the data but much later.
Have you ever faced an issue like this ?
The experiment consists in a QUCI Netty server application sending 1GB file to 6 NETTY QUIC clients. I am running the experiments
in two identical servers with high network connectivity. In one I run the server application plus 3 clients, and on the other I run the rest of the clients (3 clients).
And these are the technical description of the servers:
processor: 2 x AMD EPYC 7343 | cpu cores/threads: 32⁄64 | RAM: 128 GiB DDR4 3200 MHz | network interfaces: 2x10 Gbps | 450 GB SSD
The text was updated successfully, but these errors were encountered: