MQSeries.net :: View topic - Scaling of a Compute Node Inserting XML Message into Oracle

lennon · Posted: Wed Sep 15, 2004 10:18 pm Post subject:

We are using MQSI V2.1 with CSD2 on Solaris.
As part of the processing flow , a Compute node is being used to call an Oracle 8.1.7 Stored procedure to store the XML body into the database. (the database field is defined as a CLOB).
The code being used in the compute node to perform this operation is as follows:

BITSTREAM(OutputRoot.XML)

The message size is about 10K.

This BITSTREAM is passed as a LONG to the stored procedure which then coverts the LONG into CLOB before archiving it into the database.
All this works perfectly well when run in a single execution environment.
This operation takes about 0.2 seconds in a single execution group environment and is consistent. However it does not scale with multiple execution groups because under simulated load ,all other nodes in the message flow scale well as expected with the exception of this compute node.

The operation that takes 0.2 seconds in an unscaled environment takes 0.8 - 1.3 seconds which defeats the purpose of scaling.

There is no contention on the stored procedure side as the same procedure when invoked from a separate non MQSI program works well when invoked in parallel.

Has anyone seen this kind of behavior before ? Are there any known issues with scaling of Merant Driver for Insert Operation ?
Is there any performance impact of the number of parameters that are being passed into the stored procedure from within a compute node ??

Any thoughts / suggestions.