| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ESQL procedure execution time |
« View previous topic :: View next topic » |
| Author |
Message
|
| KoGor |
 Posted: Fri Feb 02, 2007 4:53 am Post subject: ESQL procedure execution time |
 |
|
Voyager
Joined: 09 Nov 2005
Posts: 81
Location: Moscow,Russia.
|
I have ESQL procedure and I need to measure what time it takes to execute. I call it from main function of Compute node. Now I'm trying to insert into outgoing message CURRENT_TIMESTAMP before calling the procedure and immediate after it returns control to the main function. But I always have the same TIMESTAMP ( before: TIMESTAMP '2007-02-02 15:39:28.335246' after: TIMESTAMP '2007-02-02 15:39:28.335246') and it's hard to belive that this procedure takes 0ms to execute.
Is there another way to get this execution time?
Thank you in advance! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Feb 02, 2007 4:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
CURRENT_TIMESTAMP always returns the same value within a single Compute node.
Your best bet for basic performance data is to enable and then analyze User Trace.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| KoGor |
| Posted: Fri Feb 02, 2007 5:59 am Post subject: |
|
|
Voyager
Joined: 09 Nov 2005
Posts: 81
Location: Moscow,Russia.
|
2jefflowrey: Thank you for help.
I read a long time before and totally forget about it.
I'm triyng to use UserTrace in normal mode but there is nothing what I need. Just info about main events and nothing about compute node.
For example:
2007-02-02 16:50:12.665280 4632 UserTrace BIP6061I: Parser type ''MRM'' created on behalf of node 'SDSGenerateReceiptFlow.MQInput' to handle portion of incoming message of length '3789' bytes beginning at offset '364'. Parser type selected based on value ''MRM'' from previous parser.
2007-02-02 16:50:12.707518 4632 UserTrace BIP5493W: Message, element or attribute 'USERNAME' is self-defining within parent 'Receipients'.
The message, element or attribute 'USERNAME' did not match with any corresponding artifact in the message model hence it is considered to be self-defining. If it is not intended that this message, element or attribute be self-defining, check that the message set is referenced in the message properties, or modify the message model to correspond to the instance message, or modify the instance message to correspond to the message model.
2007-02-02 16:50:12.712400 4632 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'SDSGenerateReceiptFlow.GenerateReceipt'.
2007-02-02 16:50:12.712713 4632 UserTrace BIP5493W: Message, element or attribute 'http://www.cbr.ru/sds/:Domain' is self-defining within parent 'http://www.cbr.ru/sds/:receipt'. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 02, 2007 6:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
