Loading...
Recommendations
Explore
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
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
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
Adjust the Message Storage slider so that the channel only retains the message data that you will actually need.
One limitation on message throughput is the amount of disk writes that Mirth® Connect's database must perform while processing each message. Reducing the amount of message data retained can increase throughput and decreases memory usage as well as disk usage. Production level guarantees that if an unexpected server failure occurs, any incomplete (received, but not yet fully processed) messages will be automatically recovered and processed on restart. If increased performance is needed, you can to reduce this to the Raw level, which only retains the original raw message prior to being processed by any transformer steps. Incomplete messages can still be recovered on failure, but must be done so by manually reprocessing them. Keep in mind that using destination queues requires at least Production level. 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
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 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.
