Web Player and resource pooling

Web Player and resource pooling

When planning routing and setting up resource pools some questions may arise, such as:

1. What is the best way to set up number of Web Players with different or same resource pool and what are the advantages and disadvantages of routing a certain set of analyses to specific TIBCO Spotfire Web Player?
2. If one report fails, or takes a very long time to run - will the other reports that are scheduled to run on one specific Web Player delayed and, if so, can they be moved automatically to another Web Player?
3. In a setup with several Web Players in the same resource pool and one Web Player is restarted - how long does it take until the reports assigned to that node are moved to the available one?

1. In certain situations, it may be required to route a certain set of analyses to specific TIBCO Spotfire Web Player instances under a given Node Manager without allowing any other analyses to be routed on that Node Manager. For example, a few analyses may be critical for the business with complex data operations in it, which may require large amounts of resources in terms of RAM and CPU.  Due to such analyses, there are more chances of having performance issues and which might negatively impact other working analyses. So to avoid any issues, it may be better to have a dedicated Node Manager for such expensive or important analyses where no other analyses will be allowed to route.
2. The setting concurrentUpdates in the service configuration file sets the maximum number of concurrent updates that can be executed at the same time. This is used to limit resources used by the update mechanism. Min value is 1 and max value is 10. Thus, if on the same Web player one file is taking a really long time, another one will be also loaded. And if both take long time and you have more Web Players in the same resource pool they should be loaded on the other Web Player.
3. When a Web Player goes offline/restarts, the loaded files will not stay cached. So it has to be reloaded again, and it might get picked up by another Web Player before the first Web Player is started again.The failover-delay in the Spotfire Server configuration file is somewhat interesting since enabling this will make the restarted Web Player up and running before new loads are thrown on the Web Players, and then the restarted one will get most of them??????. 

   <!-- If enabled, introduces a delay to before scheduled updates are loaded when a service starts or stops.
   If disabled, scheduled updates are reevaluated immediately. -->
   <failover-delay>
   <enabled>false</enabled>
   <!-- delay expressed in seconds -->
   <delay>300</delay>
   </failover-delay>

Manually editing the server configuration:
https://docs.tibco.com/pub/spotfire_server/10.3.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-3D77DED9-B16F-41F3-8D82-DE3FBF5DD09F.html