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

KB7605: What is the difference between the ’Maximum number of simultaneously executing segments’ and the ’Maximum segments per execution’ settings in MicroStrategy Narrowcast Server?


Community Admin

• Strategy


This knowledge base article explains the difference between the ’Maximum number of simultaneously executing segments’ and the ’Maximum segments per execution’ settings in MicroStrategy Narrowcast Server.

'Maximum number of simultaneously executing segments' and 'Maximum segments per execution' are settings in Strategy Narrowcast Server 9.4.x-10.x.
The setting in the Execution Engine editor (shown below) refers to the maximum number of segments that can run at one time. For example, if this setting was 10 and there were 100 segments to be executed the first 10 would go to the Execution Engine and the other 90 would remain in the queue. Once one of the segments finished execution then another segment would be loaded into the Execution Engine from the queue.

ka04W000000OgCUQA0_0EM440000002BvC.gif

The setting in the System Governing tab (shown below) refers to the maximum number of Segments that a service can be divided into. For example, if the segment size for a service was set to 1 and there were 10,000,000 recipients in the subscription set, then the server would perform 10,000,000 executions. This could be considered an excessive load for the execution of one service. By putting a maximum value, users can prevent services such as these from running. If this setting were set to 100,000, then users would need to change the segment size to 100 for the service in this example to run.

ka04W000000OgCUQA0_0EM440000002Bv2.gif

Comment

0 comments

Details

Knowledge Article

Published:

June 22, 2017

Last Updated:

June 22, 2017