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
After some testing with quinn we noticed that rustls most highly preferrenced cipher suite TLS13_CHACHA20_POLY1305_SHA256 is quite a bit slower than TLS13_AES_128_GCM_SHA256 and TLS13_AES_256_GCM_SHA384 on typical desktop and server hardware due to hardware acceleration for AES.
Where a quic loopback transfer with TLS13_CHACHA20_POLY1305_SHA256 maxed out at 350MB/s, it reached 520MB/s using TLS13_AES_128_GCM_SHA256 (+50%), and about 500MB/s using TLS13_AES_256_GCM_SHA384.
Can the cipher suite list in ALL_CIPHERSUITES be reordered to prefer AES cipher suites?
I feel like there will be quite a lot of people running this with default config, and might not detect that they are not reaching peak performance and efficiency.
The text was updated successfully, but these errors were encountered:
After some testing with quinn we noticed that rustls most highly preferrenced cipher suite
TLS13_CHACHA20_POLY1305_SHA256
is quite a bit slower thanTLS13_AES_128_GCM_SHA256
andTLS13_AES_256_GCM_SHA384
on typical desktop and server hardware due to hardware acceleration for AES.Where a quic loopback transfer with
TLS13_CHACHA20_POLY1305_SHA256
maxed out at 350MB/s, it reached 520MB/s usingTLS13_AES_128_GCM_SHA256
(+50%), and about 500MB/s usingTLS13_AES_256_GCM_SHA384
.Can the cipher suite list in ALL_CIPHERSUITES be reordered to prefer AES cipher suites?
I feel like there will be quite a lot of people running this with default config, and might not detect that they are not reaching peak performance and efficiency.
The text was updated successfully, but these errors were encountered: