User Level

• Authentication objects
  
• A distinct Strategy Intelligence Server user login can be used to execute reports for each subscriber. In this way, if Intelligence Server user logins have security filters defined for them, these security filters are applied to the service content.
• Strategy Narrowcast Server must request one job to the Intelligence Server for each unique authentication object in a segment. This is because the Strategy Intelligence Server appends the security filter to the 'Where' clause of the job's Structured Query Language (SQL) thereby creating a unique SQL for each job request.

Service Level

• Segment Size
  
• This setting specifies the number of subscriptions per segment in the service. At run-time, the total number of subscriptions is divided into segments of this size. The default is 100 subscriptions.
• Strategy Narrowcast Server minimizes the number of job requests to the Intelligence Server by:
  
• Inspecting the preference and authentication objects of each subscription within a segment.
• Grouping the subscriptions with identical preference and authentication objects into buckets called 'Usersets.' Each subscription in a 'Userset' receives identical content data.
• Submitting a single job request to the Intelligence Server for each 'Userset.'
• Larger segment sizes greatly reduce the number of job requests to the Strategy Intelligence Server when there is a high probability of subscriptions having identical preference objects and authentication objects.
• Segment Execution Timeout
  
• This setting specifies the timeout period for the segments in the service. The default is 1 hour.
• This setting should be set longer than the time it takes to retrieve the content data from the Strategy Intelligence Server, format it, and deliver it to each subscription in the largest segment in the service.
• When a segment times out, Strategy Narrowcast Server re-executes the segment, thus causing the job requests to be resubmitted to the Intelligence Server - the original job requests are not automatically terminated in the Intelligence Server. In the following screen shot, job 53 was resubmitted because the segment timed out, job 47 continued executing:
  

• Strategy Narrowcast Server re-executes timed out segments only when:
  
• Service Execution Timeout has not been reached.
• Maximum failover count has not been reached.

Execution Engine Level

• Maximum number of simultaneously executing segments
  
• To locate this setting, double-click on the Execution Engine:
  

• This setting specifies how many segments can execute simultaneously. The default is 10 segments.
• Only job requests associated with executing segments are submitted to the Strategy Intelligence Server.
• If the number of segments in a service exceeds this setting then some of those segments will wait in the execution queue. The setting 'Segment Execution Timeout' applies to segments waiting in queue.

System Level

• Maximum failover count
  
• To locate these settings, from the menu option 'System,' click on the desired Narrowcast system and go to 'Set Governing Settings' > Execution tab:
• This setting controls the number of times Strategy Narrowcast Server will re-execute segments that have timed out. The default is 10 attempts. Each time a segment is re-executed, Narrowcast Server resubmits the job requests to the Strategy Intelligence Server.

Information Source Level

• Maximum number of executing information objects
  
• To locate this setting, edit an Information Source, proceed to the section 'Intelligence Server,' and then click on 'Advanced Properties.' The default is 25 information objects.
• This setting controls how many information objects the Information Source processes simultaneously. For example, if the service contains four Information Objects (IO), and this setting equal two, then the Information Source will submit to the Strategy Intelligence Server job requests for only two IOs at a time.

Service Execution Type

One way to dramatically reduce the number of job requests to the Strategy Intelligence Server is to use personalized page execution mode (instead of personalized report execution which uses prompts). For more information on personalized page execution, refer to the Page Personalization and Dynamic Subscriptions chapter in the Strategy Narrowcast Server Application Designer Guide.