You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a driver that collects data from a field device using ModbusTCP protocol every 5 seconds and as the responses arrive from driver, the connected websocket clients are sent messages. There are 16 field devices and driver collects 8 data points from each device. There are 16 threads , one for each device and driver will sequentially fetch data from and send message to websocket clients.
So, every 5 seconds there are 128 messages sent via websocket, I found that Alchemy websocket has a message queue.
Is this message queue operations give rise to a 30 to 45 seconds latency in HTML5 client updates?
The text was updated successfully, but these errors were encountered:
I have a driver that collects data from a field device using ModbusTCP protocol every 5 seconds and as the responses arrive from driver, the connected websocket clients are sent messages. There are 16 field devices and driver collects 8 data points from each device. There are 16 threads , one for each device and driver will sequentially fetch data from and send message to websocket clients.
So, every 5 seconds there are 128 messages sent via websocket, I found that Alchemy websocket has a message queue.
Is this message queue operations give rise to a 30 to 45 seconds latency in HTML5 client updates?
The text was updated successfully, but these errors were encountered: