Conversation
Link the AWS-LC build the devcontainer installs to /opt/boringssl, together with ngtcp2_crypto_boringssl instead of ngtcp2_crypto_ossl. It is used throughout the process, by Boost.Asio's SSL streams as well as by HTTP/3, so the system OpenSSL is no longer linked at all. With BoringSSL, ngtcp2 configures QUIC once on the SSL_CTX and takes the SSL itself as the TLS native handle, so Http3Session no longer needs an ngtcp2_crypto_ossl_ctx next to it, nor ngtcp2_crypto_ossl_init(). tls_handshake_info() moves off the OpenSSL 3 only group name APIs. With a single-threaded server under h2load, AWS-LC needs about 55% less CPU per TLS handshake over TCP (35% over QUIC) and echoes 8-10% more MB/s on all three protocols. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link the AWS-LC build the devcontainer installs to /opt/boringssl, together with ngtcp2_crypto_boringssl instead of ngtcp2_crypto_ossl. It is used throughout the process, by Boost.Asio's SSL streams as well as by HTTP/3, so the system OpenSSL is no longer linked at all.
With BoringSSL, ngtcp2 configures QUIC once on the SSL_CTX and takes the SSL itself as the TLS native handle, so Http3Session no longer needs an ngtcp2_crypto_ossl_ctx next to it, nor ngtcp2_crypto_ossl_init(). tls_handshake_info() moves off the OpenSSL 3 only group name APIs.
With a single-threaded server under h2load, AWS-LC needs about 55% less CPU per TLS handshake over TCP (35% over QUIC) and echoes 8-10% more MB/s on all three protocols.