EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB5662: System Governing settings about segmentation in MicroStrategy Narrowcast Server Delivery Engine


Community Admin

• Strategy


How to access and set the governing settings within Narrowcast Administrator for segmentation.

To access the governing settings in the Strategy Narrowcast Administrator for Delivery Engine, users must follow the steps below:

  1. Go the System Menu and select the Narrowcast system. Select 'Set Governing Settings' from the menu.
  2. Select the Execution tab. At the bottom of the Execution tab, there is a section for Segmentation settings.

 
These settings are:

  • Maximum concurrent expansions.
  • Segment Queue sizes to trigger segmentation:
     
    At least: ###
    At most: ###
     
ka04W000000OhEIQA0_0EM440000002BxR.gif

 
 
Maximum concurrent expansions:
It is the largest number of services for which the distribution manager performs segmentation at any one time.
 
Segment queue sizes to trigger segmentation:
It controls when services are segmented based upon the current size of the segment queue. This setting can be used to ensure that the system is not overloaded by execution requests.
 
Example:
If the settings for the Segment queue are as follows:

  • Segment Queue sizes to trigger segmentation:
    At least: 10
    At most: 100

 
Suppose a first service is segmented and it puts 50 segments on the segment queue. Then a second service is segmented and it puts another 50 segments on the queue. At this point, the maximum number of segments (100, for this example) have been reached; therefore, no more services will be segmented until the queue decreases.
 
In another example, suppose a first service is segmented and it puts 6 segments on the segment queue. Then a second service is segmented and it puts another 6 segments on the queue. At this point, there will be 12 segments on the queue, bypassing the 'At least' parameter (10, for this example). Therefore, only incoming services that have a greater priority than those already on the segment queue will be segmented. (Service Priority will only be of importance if the number of segments in the queue is between the 'At least' and 'At most' parameters.)
 
 
 
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017