Sequence Performance Query

parag.s.27 · Post by **parag.s.27** » Wed Sep 26, 2007 4:08 am

I wanted to know about sequence performance.

Here I am having 100 plus small sequences that are having 4 - 5 jobs incorporated in each on an avg. Now these sub sequences are to be called in one master sequence which represents a Single Database.

What can be the best approach for moving forward: -
1.I should split this in 4 - 5 (sub master)sequences where in each of these I'll call 25 small subsequences. Later I'll incorporate these 4 - 5 sub master sequences in a single sequence.
2.I should directly go ahead and call all these 100 subsequences in a single sequence. But I think this will be more complicated and it will be more difficult to track and debug any error in it.

JoshGeorge · Post by **JoshGeorge** » Wed Sep 26, 2007 5:25 am

Modularizing and putting comments for log entries is for sure the best way. Option 2.

abhi989 · Post by **abhi989** » Wed Sep 26, 2007 11:07 am

You will also need to take into consideration that if you are firing these many jobs at the same time, CPU might run out of processing power and starts crapping out. (need to take hardware into consideration). Also logging information into the job log can be done by calling a custom routine that does that(in this routin you can put a DS log command)

parag.s.27 · Post by **parag.s.27** » Thu Sep 27, 2007 1:11 am

abhi989 wrote:You will also need to take into consideration that if you are firing these many jobs at the same time, CPU might run out of processing power and starts crapping out. (need to take hardware into consideration). Also logging information into the job log can be done by calling a custom routine that does that(in this routin you can put a DS log command)

The Hardware is selected as per the requirements only...hence it is fully compatible.

ray.wurlod · Post by **ray.wurlod** » Thu Sep 27, 2007 1:48 am

"Compatible" is an entirely different question from "enough". You can still overload compatible hardware.