Inconsistent Treatments & Caching

Follow

jlytle

• October 05, 2020 17:53

Hello, 

Recently experiencing inconsistent treatments and looks to be related to SplitIO caching.  Treatment applications work as expected when resetting IIS between calls to SplitIO. 

Any suggestions?  Is use of the "Destroy()" method necessary after each use of the service?

Thank you

 

0

• 

  Bilal Al-Shahwany

  • October 05, 2020 17:58

  Hi, If you are using .NET SDK on server side implementation, make sure you have a singleton factory instance, so everytime you need to call getTreatment, you re-use the same factory and not create new one. Therefore, no need to call Destroy() on the server side, since the SDK will continue to serve new user sessions.

  When using one factory instance, the cache will remain in the memory and will be re-used each time getTreatment is called.

  Hope that helps.

  Thanks

  Bilal

  0

  Comment actions Permalink
• 

  Mauricio Silva Vázquez

  • October 05, 2020 18:06

  Using the .NET SDK and when turning on a Split I need to restart my IIS to see the split toggled. Is this a normal behavior? Does Split refresh every X amount of seconds/minutes to get new values from the split when I have a singleton of it?

  0

  Comment actions Permalink
• 

  Bilal Al-Shahwany

  • October 05, 2020 18:12

  Hi Mauricio, the latest version of .NET SDK (6.1.5) has Streaming feature enabled which is a socket connection to split cloud that pushes any split changes to the SDK instantly, so the cache is always synched.

  If you have lower SDK versions, the polling thread runs every 5 seconds to sync the cache, so any changes in UI is synched within 5 seconds.

  If the SDK is not synching within this time, enable debug logging for the SDK to troubleshoot the issue, here is doc link on how to enable the log: https://help.split.io/hc/en-us/articles/360020240172--NET-SDK#logging

   

  Thanks

  Bilal

  0

  Comment actions Permalink

Please sign in to leave a comment.