MQSeries.net :: View topic - Time used by the ESQL in a compute node

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Time used by the ESQL in a compute node

Time used by the ESQL in a compute node

« View previous topic :: View next topic »

Author

Message

KIT_INC

Posted: Thu Oct 20, 2011 4:47 am Post subject: Time used by the ESQL in a compute node

Knight

Joined: 25 Aug 2006
Posts: 589

I am using WMB V6.1 CSD 9 on Windows. I have a message flow which spent 5 minutes in a compute node processing a very complex XML message. We like to find out which section of the code is using most of the time so that we can optimise it. We thought about inserting statements like
SET Environment.Time = CAST(CURRENT_TIMESTAMP AS CHAR FORMAT 'yyyyMMddHHmmss.sss'); at various locations of the ESQL code and output the environment later. But it is documented that we will always have the same value for CURRENT_TIMESTAMP within the node.
I am looking for suggestion on how this can be done. Is there any ESQL function that will give us the actual time as the code executes ?

lancelotlinc

Posted: Thu Oct 20, 2011 5:31 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Yes, you must make a call out to a Java jar to get the right time value.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ak04960_.htm
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

zpat

Posted: Thu Oct 20, 2011 6:10 am Post subject:

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Maybe PROPAGATE out to another compute node and return the time in a local environment variable.

mqjeff

Posted: Thu Oct 20, 2011 6:22 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Ignore all of the above advice.

Take a User Trace of the flow.

Voila.

All the timing information you need.

KIT_INC

Posted: Thu Oct 20, 2011 6:50 am Post subject:

Knight

Joined: 25 Aug 2006
Posts: 589

The original design is probably bad. The flow is using file input and output. The input file is 10 MB in size. A user trace will be huge unless we are able to get a smaller file which we are sure that exercise all the code. The source file provider is not willing to provide that at this time.

mqjeff

Posted: Thu Oct 20, 2011 7:51 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Is the file being processed in records? I.e. can you take a user trace just long enough to see one iteration of a loop... or at least make sure that usertrace is big enough to hold the LAST iteration through the loop...

Otherwise instead of trying to stick stuff into Environment and making fancy date calculations, use the esql LOG statement to write to user trace (which is otherwise disabled).

This will show you the points in your code as they get executed and create reliable timestamps for those points.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Time used by the ESQL in a compute node

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP