Startup time is more than Prodcution Run time
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 39
- Joined: Mon Feb 13, 2012 1:30 pm
Startup time is more than Prodcution Run time
Hi,
In one of my job, i can see the following -
Message: main_program: Startup time, 1:39:42; production run time, 34:23
What may be the issue here? I am loading data in 3 tables (1.5 Million, 21 Million, 13 Million)
Thanks,
Vishal Gupta
In one of my job, i can see the following -
Message: main_program: Startup time, 1:39:42; production run time, 34:23
What may be the issue here? I am loading data in 3 tables (1.5 Million, 21 Million, 13 Million)
Thanks,
Vishal Gupta
I don't think that is applicable here. We're talking about a "start up" time of over an hour and a half, not a couple of minutes when it should normally be a handful of seconds. I'm guessing this job always has this discrepancy...
I'd start by looking into what all is encompassed in that start up time. For instance, are you creating huge lookup caches?
I'd start by looking into what all is encompassed in that start up time. For instance, are you creating huge lookup caches?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 39
- Joined: Mon Feb 13, 2012 1:30 pm
I'm sure that Ray will be along eventually to school us but as Mike mentioned it seems to me it would be worthwhile to check the log timestamps to see what all of the activities were that took place during that initial 1:39:42 of run time. Unless we're in that "not accounted for elsewhere" zone and start up time also includes wind down time... or the times when rows are not flowing through the job?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can get more information about the startup by setting the environment variable APT_STARTUP_STATUS.
Startup time includes all the work done by the conductor up till the time that player processes begin execution. This includes:
And, yes, anything more than a few seconds should be cause for concern.
Startup time includes all the work done by the conductor up till the time that player processes begin execution. This includes:
- verifying licensing
composing the score from the generated OSH and configuration file
sending requests to start section leader process on each node
waiting for section leaders to respond that they've started
verifying licensing (= existence of parallel engine) on each node
distributing the score to the section leaders
And, yes, anything more than a few seconds should be cause for concern.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.