-
Notifications
You must be signed in to change notification settings - Fork 54
Description
Is this a support request?
This issue tracker is maintained by LaunchDarkly SDK developers and is intended for feedback on the SDK code. If you're not sure whether the problem you are having is specifically related to the SDK, or to the LaunchDarkly service overall, it may be more appropriate to contact the LaunchDarkly support team; they can help to investigate the problem and will consult the SDK team if necessary. You can submit a support request by going here or by emailing support@launchdarkly.com.
Note that issues filed on this issue tracker are publicly accessible. Do not provide any private account information on your issues. If your problem is specific to your account, you should submit a support request as described above.
Describe the bug
Upgrading to version 8.11.0 or greater causes the client initialization to take much longer. We noticed that the time to initialize on some of our services went from ~1 second to 15-20 seconds.
To reproduce
Upgrade to version 8.11.0 of the sdk on service. I have noticed that this problem is much more noticeable in our production environment than staging, likely due to the amount of feature flags defined in our production environment.
Expected behavior
The time to initialize stay consistently at about 1-2 seconds.
Logs
After upgrading to 8.12.0.

SDK version
After testing different version it appears that this happens on any version >= 8.11.0. I have pinned our version to 8.10.2 for now and it does not happen.
Language version, developer tools
This happened on 2 different services, one running Ruby 3.4.8 and one running Ruby 3.3.8.
OS/platform
Running in docker containers based on the official Debian Bookworm Ruby images.
Additional context
I suspect that this change is causing the performance regression.
