Vous êtes sur la page 1sur 23

limit

activation limit

MAX JOBS

maximum number of process instances that can concurrently be loaded into memory

ACTIVATION LIMIT

once a process instance is loaded, it must remain in memory until it completes

FLOW LIMIT

maximum number of concurrently running process instance to start before suspending the process starter

Flow Limit Demystified

flow limit to your rescue

Flow Limit Demystified

FLOW_CONTROLLED flow limit =1

FLOW_CONTROLLED state

WHEN?

When a process engine reaches the Flow Limit, it is placed in this state

The process engine can continue executing existing process instances, but new process instances are not allowed.

WHAT?

Leaving FLOW_CONTROLLED state

A process engine leaves this state when the number of process instances completed is approximately half of the value specified for the Flow Limit

Specifics : HTTP Receiver

When Flow Limit is set on a process containing this starter, the maximum number of incoming requests is limited to

Recommended Usage

and to control the flow of incoming HTTP requests instead of using the Flow Limit property

Use

Max Jobs Demystified


Max Jobs = 5

DISK

MEMORY

Max Jobs Demystified


If you have sufficient system resources and do not expect incoming events to exceed the limits of your system, specify as which allows the engine to create an unbounded number of process instances and eliminates the overhead of paging

Activation Limit Demystified


It is useful if you wish to specify sequential processing of incoming events or if you want to enforce limited concurrent execution of process instances

Effects of configurations

Max Jobs

Use Activation Limit

Flow Limit

Unlimited number of process instances can be created and can be concurrently loaded into the memory Use of Activation limit is ignored when Max Jobs is 0

Effects of configurations

Max Jobs

Use Activation Limit

Flow Limit

Allows n process instances to be created before placing process starter in flow controlled state No paging of process instances Use of Activation limit is ignored when Max Jobs is 0

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

Allows n process instances to be created before placing process starter in flow controlled state
One process instance is loaded into memory at a time and kept there until it completes its execution This guarantees incoming events are processed in the order in which they occur

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

There is no limit on the number of process instances that can be created


One process instance is loaded into memory at a time and kept there until it completes its execution This guarantees incoming events are processed in the order in which they occur

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

Allows n process instances to be created before placing process starter in flow controlled state One process instance is loaded into memory at a time
Incoming events can be processed in any order as process instances are not kept in memory until they complete execution

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

There is no limit on the number of process instances that can be created


m process instances can be loaded into memory at a time and processed concurrently

Ensures limited amount of concurrent processing. Useful when you have limited resources like database connections. Set m to a small number, use activation limit. Each loaded process uses a resource until it completes. Once it completes, a new process is loaded and would use the same resource

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

Allows n process instances to be created before placing process starter in flow controlled state
m process instances can be loaded into memory at a time and processed concurrently

Ensures limited amount of concurrent processing. Useful when you have limited resources like database connections. Set m to a small number, use activation limit. Each loaded process uses a resource until it completes. Once it completes, a new process is loaded and would use the same resource

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

There is no limit on the number of process instances that can be created


m process instances can be loaded into memory at a time and processed concurrently

After m process instances are created, new process instances are paged to disk. There is no guarantee of the order in which the process instances are executed

Effects of configurations
Max Jobs
Use Activation Limit

Flow Limit

Allows n process instances to be created before placing process starter in flow controlled state
m process instances can be loaded into memory at a time and processed concurrently

After m process instances are created, new process instances are paged to disk. There is no guarantee of the order in which the process instances are executed

Vous aimerez peut-être aussi