Identification of them is the first step, after that you can work on ameliorating them. What's going on in the Java transformers? Any way to replace them with native DataStage functionality?
-craig
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote: What's going on in the Java transformers? Any way to replace them with native DataStage functionality? ...
Hi Craig,
The java transformer has the code to generate XPATH,element name and value.We are using this as the xsd of the XML's that we get comes from over 1000 applications and all have their own structures.
The other java transformer does cleansing of XML.
So its not possible to parse even with XML assembly stage also.
The lag is being caused by the way buffers work in DataStage and is an essential.
You might want to have a look at the "score" to ensure that no unnecessary repartitioning is happening.
Also, if your Transformer is not implementing any business logic and is just performing minor conversions, you might want to have a look at the Modify stage.
If performance is a very critical facet and you have substantial memory at your disposal, try to increase the buffer size.
Not too sure if it would be a wise idea to increase the APT_BUFFER_FREE_RUN but it might help. Trial & error will give you a good idea
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.