Replies: 1 comment 1 reply
-
TLS context is only used by the s3 crt client. That being said it shouldn't be taking that long to initialize it. Can you provide a quick repo and details about your environment that can help us look into this? How long exactly is this taking to initialize with and without TLS context? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear all,
when trying to figure out why the initialization of the API via
initAPI(options)
takes so long, I found that the call to create theAws::Crt::Io::TlsContext
context is rather slow (https://github.com/aws/aws-sdk-cpp/blob/main/src/aws-cpp-sdk-core/source/Aws.cpp#L101). When digging deeper into the code, I could not find when this TLS context will ever be used again, because it is just used to create the TLS options which are then set viaSetDefaultTlsConnectionOptions
(https://github.com/aws/aws-sdk-cpp/blob/main/src/aws-cpp-sdk-core/source/Aws.cpp#L103 and https://github.com/aws/aws-sdk-cpp/blob/main/src/aws-cpp-sdk-core/source/Globals.cpp#L40) and live as a static member variableg_defaultTlsConnectionOptions
in Globals.cpp. The only way this variable is accessed is viaGetDefaultTlsConnectionOptions()
(https://github.com/aws/aws-sdk-cpp/blob/main/src/aws-cpp-sdk-core/source/Globals.cpp#L43), which is never called from inside the aws cpp sdk. So I am wondering what this is about? Is there some usage of this static member that I cannot see? To me it does not seem to make a difference when I just comment the whole TLS initialization section, except that the call to initAPI() gets much faster.Thanks!
Beta Was this translation helpful? Give feedback.
All reactions