Hello All,
Does anyone have any idea about how much space should be allocated to the /tmp and scratch area on unix for optimum performance of Datastage jobs.
We are using Datastage 6.0 with PX.
Thanks.
Raj
tmp and scratch space
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
More! 
This question is in the same league as "how long is a piece of string?". It really does depend on what you're doing.
Ideally you shouldn't need to use /tmp at all with PX, as temp space for the Engine is configurable (via UVTEMP in uvconfig) and scratch space per node is configurable in PX configuration files. Leave /tmp for purely UNIX temp space.
As to how much, this will be driven by data volumes and what you're doing with the data. For example, if you're sorting you'll need more scratch space than if you're not sorting.
This question is in the same league as "how long is a piece of string?". It really does depend on what you're doing.
Ideally you shouldn't need to use /tmp at all with PX, as temp space for the Engine is configurable (via UVTEMP in uvconfig) and scratch space per node is configurable in PX configuration files. Leave /tmp for purely UNIX temp space.
As to how much, this will be driven by data volumes and what you're doing with the data. For example, if you're sorting you'll need more scratch space than if you're not sorting.
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.