| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BATCHINT |
« View previous topic :: View next topic » |
| Author |
Message
|
| kavithadhevi |
 Posted: Fri Aug 01, 2003 7:50 am Post subject: BATCHINT |
 |
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
I am confused as how BATCHINT works. 
If i set my BATCHINT to 0 and BATCHSZ as 3. According to the docs,
| Quote: |
| if there are no more messages in xmitq , it would wait until BATCHINT expires. |
My question is :
Whats happens with BATCHINT set to 0, does it expire immediately when the above condition is met or sits and waits forever.
Please share your thoughts.
_________________
Thanks in Advance. 
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
 |
| skn |
| Posted: Fri Aug 01, 2003 8:25 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
| If u specify the BATCHINT as 0 then sync point will be taken only when the no of messages transmitted equals the value set in BATCHSZ. |
|
| Back to top |
|
|
| kavithadhevi |
| Posted: Fri Aug 01, 2003 10:11 am Post subject: |
|
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
What if say i haven't got the full set of messages mentioned in the BATCHSZ ? What happends then to the BATCHINT?
_________________
Thanks in Advance.
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
|
| skn |
| Posted: Fri Aug 01, 2003 10:16 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
| it waits for the BATCHINT to expire from the point when there are no messages in the transmission queue and then does a syncpoint . |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Aug 01, 2003 7:22 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
0 means no batch interval.
Say your batch size is 1,00,000 and your batch interval is 0. If one message gets put to the XMIT queue, the MCA will grab it and ship it across. It then goes back to the XMIT queue to get the next message. If it does not find one, it will wait for batch interval seconds, in our case zero seconds, for another message before committing whatever it may have already sent.
In this example, even though you set the batch size to 1,000,000, your effective batch size was only 1.
A low batch interval means your messages will be shipped across and committed more often, thus being made available to the remote side that much faster. But this comes at the expense of more processing as the MCAs must commit more often.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
