workflow and number of concurrent job instances

Hi All,

Just wanted to know if there is a limit on the number of Job instances that can be created/ can exist concurrent ly for a given workflow?

Is there a way to limit the number of job instances.

Your responses are much appriciated.

Regards
AT

Find more posts tagged with

Comments

Agarwal

Hi All,

Just wanted to know if there is a limit on the number of Job instances that can be created/ can exist concurrent ly for a given workflow?

Is there a way to limit the number of job instances.

Your responses are much appriciated.

Regards
AT

There can be n number of job instances.
Why do you want to limit the number of job instances, what are you trying to achieve from this ?

Thanks
Akshat Agarwal

Antharix

My intension is to have a control on the number of concurrent jobs that can be active at a given point in time. By doing this, I want to control the load on the Wrokflow engine and avoid instances were Teamsite becomes slow or a need arises to admin TS environment.

Natasha

My intension is to have a control on the number of concurrent jobs that can be active at a given point in time. By doing this, I want to control the load on the Wrokflow engine and avoid instances were Teamsite becomes slow or a need arises to admin TS environment.

Hi,

I found something related to this in the workflow manual. You can restrict the no of job instances that can be started from the parent workflow through a setting in iw.cfg.

[workflow]
The maximum depth of nesting allowed for nested jobs (wftask);defaults to 3. Values less than 1 are ignored.
wftask_nesting_depth_allowed=3

All the above is commented in the iw.cfg and I think one has to uncomment it and set it to the desired value.

I havent tried it so the best way is to edit this value and in the parent job, get the value of nested jobs started from the parent to verify it.

Thanks,
Natasha.

Adam Stoller

Hi,

I found something related to this in the workflow manual. You can restrict the no of job instances that can be started from the parent workflow through a setting in iw.cfg.

[workflow]
The maximum depth of nesting allowed for nested jobs (wftask);defaults to 3. Values less than 1 are ignored.
wftask_nesting_depth_allowed=3

All the above is commented in the iw.cfg and I think one has to uncomment it and set it to the desired value.

I havent tried it so the best way is to edit this value and in the parent job, get the value of nested jobs started from the parent to verify it.

Thanks,
Natasha.

I believe that controls the number of children / grand-children / great-grand-children jobs that can be invoked as nested jobs and not the number of children jobs which can be initiated for a single parent, nor the number of jobs that can be invoked at the parent level.

Adam Stoller

My intension is to have a control on the number of concurrent jobs that can be active at a given point in time. By doing this, I want to control the load on the Wrokflow engine and avoid instances were Teamsite becomes slow or a need arises to admin TS environment.

If you are facing problems with performance due to the number of active jobs - either you need to make sure that you don't have a lot of stranded jobs sitting out in the system (see Nipper's call-to-arms about using timeouts) or you have an undersized system in terms of memory, disk, and/or CPU -- or you have an ancient version of TeamSite in which the number of active tasks within the system could cause performance problems significantly earlier than the current system's threshold.

Antharix

Thanks Natasha! and Ghoti!

I will check the options suggested.

The current environment is TS 6.7.1 on solaris with 8GB of RAM, 4CPU and I was considering suggesting of memory upgrade.

Thanks Again.

Adam Stoller

Thanks Natasha! and Ghoti!

I will check the options suggested.

The current environment is TS 6.7.1 on solaris with 8GB of RAM, 4CPU and I was considering suggesting of memory upgrade.

Thanks Again.

How many active jobs do you currently have on the system?
Are you seeing performance issues now? Or just trying to plan for a potential future issue without any real data to indicate that you need to do anything?