Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system.

Mirth® Connect by NextGen Healthcare User Guide

Enable destination queuing if you do not need to respond to the originating system from your destination.

All destination connectors support queuing. Queuing is important for re-attempting to send messages if they do not succeed at first, but can also improve channel performance. Without queuing, the message send attempt will occur on the main message processing thread for the channel, which will block any new messages from being processed (unless the Max Processing Threads is increased, see below). This can significantly improve channel performance if the system you are sending to is slow to respond. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another.

Clearing this box will allow adjacent destinations to execute in parallel, potentially improving performance. When using several destinations, you can configure some to execute in order and others to execute in parallel. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Increase the Queue Threads value if the downstream system can accept multiple concurrent connections.

This setting controls how many messages can be simultaneously retrieved from the outbound queue to attempt to send and is similar to the Max Processing Threads setting described above. As with the Max Processing Threads setting, the default value is 1, and increasing the value will no longer guarantee the order in which queued messages are processed. However, the "Thread Assignment Variable" setting can be used to assign messages to a particular queue thread, thus guaranteeing the send order of all messages assigned to a particular thread (unless "Rotate Queue" is set to "Yes"). Users wanting to increase outbound threads can start with 2-10 and increase or decrease from there until reaching maximum throughput. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time

This setting controls how many messages the channel can process simultaneously (on separate CPU threads). The default value is 1, which means that only one message can be processed by the channel at a time and also guarantees that messages are sent out from the channel in the order that they are received. Increasing this value eliminates the order guarantee, but can greatly increase throughput when a large number of messages is received in a short amount of time. Setting this value too high however, can harm throughput. Keep in mind that this setting controls how many CPU threads are used by the channel. So, it is important to consider how many threads the CPU can execute concurrently as well as how much of the CPU's resources are needed by other channels/processes. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Channel Performance

Adjust the Message Storage slider so that the channel only retains the message data that you will actually need. If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage. Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system. Enable destination queuing if you do not need to respond to the originating system from your destination. Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time Increase the Queue Threads value if the downstream system can accept multiple concurrent connections. Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another. Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel. Adjust the Message Storage slider so that the cha

Mirth® Connect by NextGen Healthcare User Guide

Source Connector

Every channel has exactly one source connector which gets data into Mirth® Connect from an external system. The source connector is configured on the Source Tab within the Edit Channel View. In addition to the standard Connector Components, source connectors include: A Source Queue that can be enabled or disabled. When enabled, the channel acts as a store-and-forward service that can receive messages and send acknowledgements immediately to the originating system, without having to wait for the message to process through the entire channel. A Batch Processor that can be enabled or disabled. When enabled, the channel takes any incoming data and splits it into multiple messages that each proceed discretely through the channel. See Batch Processing for additional information. A Response Selector that determines what response to send back to the originating system, if applicable. You can choose to auto-generate a response based on the inbound data type of the source transformer. You can al

Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system.

Recommendations

Enable destination queuing if you do not need to respond to the originating system from your destination.

Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another.

Increase the Queue Threads value if the downstream system can accept multiple concurrent connections.

Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time

Channel Performance

Source Connector

Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system.

Enable destination queuing if you do not need to respond to the originating system from your destination.

Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another.

Increase the Queue Threads value if the downstream system can accept multiple concurrent connections.

Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time

Channel Performance

Source Connector