Elevated SDK_READY_TIMED_OUT rate since January 2021

Follow

Dmaas

• February 02, 2021 19:38
• Edited

Hi - Our mobile app is seeing about twice the normal rate of SDK_READY timeouts since about January 10, 2021. It's currently affecting ~0.6% of daily active users. Just wondering if there is anything we can do to improve availability of Split for mobile clients.

- We have already increased the default timeouts as follows:

readyTimeout: 16

requestTimeoutBeforeReady: 8

 

- The timeouts occur mostly in the U.S., Taiwan, Korea, and mainland China. (our user base is skewed towards East Asia, and we are wondering if Fastly has spotty connectivity there)

 

- Our app uses CloudFlare for our own back-end API, which has great connectivity. We are wondering if it is possible to proxy Split.io through our CloudFlare network? (Is there some extra feature we can unlock to allow Split to present its API on a custom domain?)

0

• 

  Bilal Al-Shahwany

  • February 02, 2021 20:33

  Hi, You can run Split Synchronizer in Proxy mode inside your network, then update the SDK endpoints of mobile SDK to point to Synchronizer host, if you can insert the headers needed for Fastly CDN to cache 
  Synchronizer payload back, it will improve the performance.

  Synchronizer doc: https://help.split.io/hc/en-us/articles/360019686092-Split-synchronizer-proxy

  How to use SDK with Synchronizer proxy: https://help.split.io/hc/en-us/articles/360053243551-General-SDK-How-to-use-Split-SDKs-with-Synchronizer-Proxy-mode-

  Thanks

  Bilal

  0

  Comment actions Permalink

Please sign in to leave a comment.