In most medical messaging applications, a small amount of latency is acceptable. In Connexion, a queue will ‘sleep’ once it has processed all available messages. The sleep interval (‘empty queue sleep timeout’) has a minimum value of 5 seconds. The queue will immediately wake when new messages are received, unless those messages arrive via:
Branch operation: Messages are branched from another channel.
Secure Send operation: Messages are received from a secure sender device.
Remote Agent Sender: Messages are received from a remote agent.
We have introduced a new feature which will immediately wake a sleeping queue after receiving messages from a secure sender or remote agent. This allows for a very low latency when messages traverse Remote Agent(s) and Connexion servers.
There are two steps to enabling low latency. The first is to verify the app-level setting WakeQueuesOnRemoteMessageReceive is set to true. This setting is found in the appsettings.config file in the application executable directory.
The second step is to visit each channel in the entire workflow and ensure no devices are configured for caching. Specifically, the Remote Agent Sender device can introduce latency when caching is enabled.
For the Remote Agent Sender and Secure Sender devices, you will get the best performance and lowest latency by enabling Batch mode on the upstream queue. When the upstream queue is operating in Batch mode, these devices disable internal caching.
Learn more about Batch Mode.