Results 2 comments of Dimitar Haralanov

@kovidgoyal I imagine this improvement would have no impact if you are in a tmux session?

@arekt I believe as a temporary workaround solution you could re-initialize the LaunchDarkly client in the `startup` Sidekiq hook, since [it runs after](https://github.com/sidekiq/sidekiq/blob/v7.2.4/lib/sidekiq/cli.rb#L104-L108) `Process.warmup` e.g.: ```ruby Sidekiq.configure_server do |config| config.on(:startup)...