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

Mirth® Connect by NextGen Healthcare User Guide

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.

This feature has been available in the JavaScript user API since version 3.1.0: if (sourceMap.get("contextPath") == "/path1") { destinationSet.removeAllExcept([1]);} A less efficient pattern used prior to version 3.1.0 was to filter the message on all destinations except the desired destination. This approach consumes more disk space as the message is copied to each destination before the filtering takes place. The Destination Set Filter will ensure that the message is only processed and stored by the desired destination. Since version 3.5.0, it can also be leveraged without writing any code: 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

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

If you do not need to send back a response to the originating system, or the response does not need to come from one of your destinations, consider turning the "Source Queue" ON in your source connector. This lets the channel respond to the originating system immediately on message receipt, rather than waiting for the message to finish processing. This can increase your channel's overall throughput. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage.

When a channel processes a message, copies of the message content are made in memory at various steps in which the message is transformed. Depending on the message storage mode, multiple copies of the transformed content are also written to the disk/database. Due to this, large messages can quickly consume memory and can cause out-of-memory errors if one is not careful. An attachment handler can mitigate these problems by extracting the bulk of the message content that does not need to undergo transformation while passing through the channel. For more information about attachment handlers, please see the official User Guide. Parent topic: Channel Performance

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

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

Recommendations

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.

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

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

If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage.

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

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.

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

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

If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage.

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