DSXchange

My job is designed as below.
We get around 2million records into the queue almost in less time. Our job not able to consume fast enough and MQ getting overloaded. Finally it job got aborted. When I checked the processing speed, job able to process 1000 records/second. What type of tuning can i do in the job? Can i know which stage might be creating this hit?
Our job has transaction count as 1. It does not process in batch mode. Any pointers are invited.

What is the error message?
Try to increase the transaction count too.

It is not ginving any error message. Our concern is slowness. Job is working fine. We want the job to process faster. I cant increase transaction count as it is message by message processing. It will create the duplicates at end if i do process in batch mode.

Are you able to quantify the slowest part of the transformation process? Can you be sure that act of writing back to the MQ queue is not what limits you to 1000 records/second? What about the Transformer? You didn't even begin to describe what's going on in there.

Imagine if the job looked like this:

MQ --> SEQ

and

SEQ --> MQ

You could measure the speed of reading the queue and the spead of writing to the queue. Whatever logic you then put between

MQ --> ........whatever..............--> MQ

is only going to slow your job down further. You're going to need to determine what stages impact the performance the most. I would start with MQ --> XML input stage and see what the rows/second achieves. Then add the Transformer and output to /dev/null and see what speed reduction occurs. I don't know the purpose of the funnel, but I keep going. Figure out where performance becomes unacceptable.

Could you please specify where and how to specify the Transaction Count property.

Hi,

Trasnaction size is present in the database stage. Check the db stage where you are writing the data.