DCWRITEDAEMON

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
anupam
Participant
Posts: 172
Joined: Fri Apr 04, 2003 10:51 pm
Location: India

DCWRITEDAEMON

Post by anupam »

What should be the ideal value for "DCWRITEDAEMON"??
How does the write daemon pause between writes effect the performance.
----------------
Rgds,
Anupam
----------------
The future is not something we enter. The future is something we create.
sanjay
Premium Member
Premium Member
Posts: 203
Joined: Fri Apr 23, 2004 2:22 am

Re: DCWRITEDAEMON

Post by sanjay »

ideal value should be 20000





anupam wrote:What should be the ideal value for "DCWRITEDAEMON"??
How does the write daemon pause between writes effect the performance.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

On a single CPU machine DCWRITEDAEMON should not be set too low (say not below 10). This is the multiple of 10 milliseconds that the daemon pauses between writes.

On a multiple CPU machine lower values are OK.

High values, like the 20000 suggested by sanjay, mean that it can take up to 200 seconds (that's over 3 minutes) for a write to a cached hashed file to be flushed to disk - way too long in my opinion.

Full details are to be found in the Technical Bulletin Hashed Stage Disk Caching (dsdskche.pdf), which is one of the DataStage manuals. In particular, consult the section called Considerations for Performance.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
anupam
Participant
Posts: 172
Joined: Fri Apr 04, 2003 10:51 pm
Location: India

Post by anupam »

We are having 24 CPU Sun Microsystems sun4u Sun Fire 6800 Server. What should be the value DCWRITEDAEMON for this kind of server.

What are the dependent things which are going to be effected once we make changes in this parameter.

Are there any other associated parameters also which needs to be changed along with this parameter to get better performance.
----------------
Rgds,
Anupam
----------------
The future is not something we enter. The future is something we create.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

10. This means that the writer daemon pauses 100 milliseconds after each write.

There are no dependencies, unless you need immediate update of the hashed file, in which case you probably want to use private link cache rather than shared cache.

Except, of course, that DCWRITEDAEMON must be 1 for this mechanism to work at all.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
desais_2001
Participant
Posts: 9
Joined: Fri Feb 28, 2003 3:52 am
Location: India

Post by desais_2001 »

ray.wurlod wrote:10. This means that the writer daemon pauses 100 milliseconds after each write.

There are no dependencies, unless you need immediate update of the hashed file, in which case you probably want to use private link cache rather than shared cache.

Except, of course, that DCWRITEDAEMON must be 1 for this mechanism to work at all.
Hello Ray,

Thank you very much for your reply.

We have observed server getting hang when set the value to 1000 in 24 CPU machine. Behaviour was very strange and we were forced to set back the default value.

We appreciate your explanation that the value is influence by the NO.of CPU's on the server. HIgher the number and value can be set to as low as
1.

Thanks once again.

Sanjay Desai / Anupam Singh.
Sanjay Desai
Post Reply