How to make recovery easier after Web Player crashes due to high load

How to make recovery easier after Web Player crashes due to high load

When using Scheduled updates to load a file if the Web Player crashes you can follow the suggestions bellow to make the recovery easier and mitigate the effects of crashing instance:

1. Reduce the proportion of the users affected by the crash
2. Enable caching of data on disk. 

Reduce the proportion of the users affected by the crash

On the same node manager machine you can create another Web Player and place it in the same resource pool as the original one. And load the file on both Web Players.

Because you have more than one user using this file the footprint of the file loaded on two Web Players will not be noticeable, and if a crash happens you will only lose about half of the sessions. 

Also these Web Player can share the same cache.
This approach doesn't require allocation of any additional resources.

Enable caching of data on disk for Scheduled Updates

To enable this you need to enter the Web Player Service configuration file Spotfire.Dxp.Worker.Web.config:

https://docs.tibco.com/pub/spotfire_server/10.7.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-A343C730-DBA1-4427-B800-E54EE944D04D.html

Modify the setting for scheduled updates:
scheduledUpdates > cacheSettings > enabled True.
The default value is set to False. 

If the data used in the analyses takes a long time to load, so will the analyses. Therefore, it is possible to cache data from scheduled analyses on disk so that the analyses reload faster on restart. 

Depending on how often the file is reloaded you can modify the value for maxAgeMinutes. This value should depend on how often the file is updated
The default value is 1440 minutes (one day). 

Web Player Service configuration file in documentation:

https://docs.tibco.com/pub/spotfire_server/10.7.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-A343C730-DBA1-4427-B800-E54EE944D04D.html