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 have implemented a tunnel application for TCP sockets where the server runs quiche and the client runs openssl 3.2.
The streams are server initiated.
I am testing the throughput with 57MB file sent with nc and received on the other side with nc >/dev/null, in a 100M LAN connection.
The performance is about 1MB/s over the tunnel, and 10MB/s over the direct connection, and I'm trying to figure if there is any low hanging fruit to fix, particularly at the openssl (peer) side, while I couldn't find a setting on openssl CTX or SSL objects to adjust many parameters like in Quiche.
Hi!
I have implemented a tunnel application for TCP sockets where the server runs quiche and the client runs openssl 3.2.
The streams are server initiated.
I am testing the throughput with 57MB file sent with nc and received on the other side with nc >/dev/null, in a 100M LAN connection.
The performance is about 1MB/s over the tunnel, and 10MB/s over the direct connection, and I'm trying to figure if there is any low hanging fruit to fix, particularly at the openssl (peer) side, while I couldn't find a setting on openssl CTX or SSL objects to adjust many parameters like in Quiche.
I am not CPU bounded (<5%).
The text was updated successfully, but these errors were encountered: