Hello @Laimiux! Thanks for your contribution.

Before moving forward, can you please tell what is the impact of the OkHttp initialization on the overall Datadog SDK initialization duration in your app?

As I mentioned here, for our sample app running on emulator it is around 1%.

For more context https://www.zacsweers.dev/dagger-party-tricks-deferred-okhttp-init/
OkHttpClient initialization can take upwards of 100ms on some Android devices in the wild due to its use of TrustManagerFactory. Initializing the Cache is also not free, as it creates an internal Executor and may incur some disk IO if you want to prepare a cache directory for it first.

Yes, but this article talks about generic setup, so it is a generic advice. Datadog SDK have a specific setup which doesn't use cache. SDK indeed is using TLS, so TrustManagerFactory will be invoked and the particular provider backing it up depends on the OEM (that is why its initialization time may vary), but on the chart you've posted here percentile is pretty much uniformed (so there are probably no spikes in the initialization duration for different OEMs due to runtime implementation issues).

Hello @Laimiux! Thanks for your contribution.

Before moving forward, can you please tell what is the impact of the OkHttp initialization on the overall Datadog SDK initialization duration in your app?

As I mentioned here, for our sample app running on emulator it is around 1%.

For more context https://www.zacsweers.dev/dagger-party-tricks-deferred-okhttp-init/
OkHttpClient initialization can take upwards of 100ms on some Android devices in the wild due to its use of TrustManagerFactory. Initializing the Cache is also not free, as it creates an internal Executor and may incur some disk IO if you want to prepare a cache directory for it first.

Yes, but this article talks about generic setup, so it is a generic advice. Datadog SDK have a specific setup which doesn't use cache. SDK indeed is using TLS, so TrustManagerFactory will be invoked and the particular provider backing it up depends on the OEM (that is why its initialization time may vary), but on the chart you've posted here percentile is pretty much uniformed (so there are probably no spikes in the initialization duration for different OEMs due to runtime implementation issues).

I see it take about ~9% of total initialization. While the other areas are bigger, this one is easy to address.

Hello @Laimiux. Thanks for your contribution.

Since we are using Gitlab CI, CI checks won't run from the forks, so I will pull your change and push it to the repo by myself and open a new PR.

Closing in favour of #2829.