Queue Matching vs. Batch block

Post Reply
Posts: 6
Joined: Sat Jul 16, 2016 2:33 pm
First Name: Sanjay
Last Name: Jain
Location: Washington DC

Queue Matching vs. Batch block

Post by sanjay_jain » Thu Feb 07, 2019 4:19 pm

If we have a model where a job splits in to three parallel paths and combines back into one, and all the queues in the 3 parallel paths are FIFO, is there any advantage to using the Queue Matching block before the Batch block? The batch block should be able to work fine even with "Batch Items into a Single Item" option selected.

If the 3 parallel paths were not using FIFO queues, one can still use the Batch block without the Queue Matching block, except now the Batch block will have to use the option "Match Items into a Single Item" option to ensure that the components of the same batch join together.

The only advantage in the specific case appears to be in collecting the statistics for waiting time that a Queue Matching block will provide but a Batch block would not.

Is that the correct understanding that in the above cases Queue Matching block is not offering any advantage in representing the process other than the waiting statistics?

Posts: 74
Joined: Thu Apr 27, 2000 12:00 am
First Name: Dave
Last Name: Krahl

Re: Queue Matching vs. Batch block

Post by davek » Fri Feb 08, 2019 9:25 am


Yes, you are correct. There is some overlap in functionality between the Batch and Queue Matching. The Queue Matching is quite a bit more powerful and you may want to consider using that if you think you might want to take advantage of its additional features in the future.

Dave Krahl
Kromite LLC
https://www.youtube.com/channel/UC1kfVS ... subscriber

Post Reply