Hi,
I have enabled Row -Buffering, inter-process, in my jobs.
In the Job prperties (Performance tab) I am unable to set
Buffer Siez > 1024 Kb.
If I type , say 4096, it changes back to 1024 as I tab out of it.
Anyways, I am using a Job Parameter also to set the IPC buffer size at individual IPCs.
Which one will be ffective, the one at individual IPCs or the Job level?
Also this 'Kb' 0 Kilo Bits or Kilo Bytes.
Acco to me Kb = Kile Bits and KB = Kile Bytes.
Thx for ur answers.
IPC Buffer Size not exceeding 1024Kb
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 273
- Joined: Wed Oct 18, 2006 12:20 pm
- Location: Porto
The lower level definition will take precedence. But setting a buffer to such a high value will have no benefit to job speed at all, in fact it might even cause the job to run slower.
to quote myself from some thread a long time ago:
to quote myself from some thread a long time ago:
So usually whether your buffer is sink-sized, bathtub-sized or swimming-pool sized makes no difference to the actual processing rates, but allocating large buffers will waste memory.ArndW wrote:...you might not be using explicit IPC stages, but by specifying inter-process buffering you are effectively making all of your active stages into separate processes that communicate with the other stages via named pipes - so you are ending up doing IPC.
A pipe between processes can be visualized something like a bathtub. The writing process fills the tub with water, the reading process is the drain and empties the bathtub. Your buffer size is the size of the bathtub. If the filler & emptier are working at about the same speed, then the size of the bathtub really doesn't matter. The buffering effect comes when one or the other only works in bursts; then you want the tub to be full enough to let the draining continue when filling stops or that there is enough room to fill up for a while if the draining stops.
The timeout is just used as an abort. If the tub is empty/full and the waiting process has to wait for longer than the the timeout interval an error is raised - the assumption is that the something has gone wrong with one of the processes and the job is made to abort.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 273
- Joined: Wed Oct 18, 2006 12:20 pm
- Location: Porto
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
In DataStage, KB is always 1,024 bytes, MB is always 1,024,576 bytes, and GB is 1,073,741,824 bytes. Never bits.
Or 1,024; 10,24,576 and 1,07,37,41,824 on the sub-continent!![Wink :wink:](./images/smilies/icon_wink.gif)
Or 1,024; 10,24,576 and 1,07,37,41,824 on the sub-continent!
![Wink :wink:](./images/smilies/icon_wink.gif)
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.