Support Board
Date/Time: Tue, 26 Nov 2024 19:12:52 +0000
Data Lagging Rithmic DTC
View Count: 694
| [2023-10-24 16:58:16] |
| PeteB - Posts: 17 |
|
Hello. The issue is I'm getting data lagging for several minutes. My internet connection speed is normal and all other apps on my machine are running normally. I connected via Rithmic Pro and it too is running normally. I opened an issue with my broker and no problems have been reported to them. I updated to the current Sierra Charts release and restarted only a single instance of Sierra but problem persists. Sierra ran good last night and there have been no changes on my machine since then. My account is paid up as well. I've attached the detailed heartbeat log. Thanks, Daniel Billing |
 sierra-heartbeat-log-lag-issue.txt - Attached On 2023-10-24 16:55:56 UTC - Size: 96.75 KB - 286 views |
| [2023-10-24 17:05:52] |
| PeteB - Posts: 17 |
|
Disabling Denali (Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Chart Data Feeds) resolves the lagging.
|
| [2023-10-24 17:18:13] |
| PeteB - Posts: 17 |
|
When I add a second instance also with denali disabled the problem begins again on both instances. It resolves when the second instance is disconnected.
|
| [2023-10-24 20:23:55] |
| John - SC Support - Posts: 36301 |
|
The reason you are having the issue with the Rithmic data when you are connected more than once is because you are only allowed to have a single connection to Rithmic. We will look over the Message Log and see if there is something that shows an issue. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-10-24 21:54:24] |
| Sierra_Chart Engineering - Posts: 17182 |
|
We only see this one delay in the log: Denali Data Feed (Market Orders Data) | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=4, NumberOfOutstandingSendBuffers=10, TransmissionDelayInMilliseconds=330, ServerSendBufferSizeInBytes=44158, ActualMessageDelay=6.2 seconds, DataCompRatio=3.14, UncompressedBytes=137741, CompressionTime=0.000812(secs), NumCompressions=13, Source=10.10.20.123, MaxSendBufferSize=123986, MaxSendBufferSizeDateTime=2023-10-24 16:52:29 | 2023-10-24 12:52:38.115 If you had a problem more than this incident, it was not data feed related. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-10-25 14:38:38] |
| PeteB - Posts: 17 |
|
Hello. I am able to connect normally to Denali today with no changes on my end. Additional info: (1) Regarding reply "The reason you are having the issue with the Rithmic data when you are connected more than once is because you are only allowed to have a single connection to Rithmic." This is incorrect. The additional connection in question was a Sierra intra-instance DTC connection only, not an additional socket to Rithmic. (2) Shown below are log records from the attached log file showing transmission and actualmessage delays. Why do you say that all delays except the 6.2 second delay are normal? Many thanks $ grep -G ActualMessageDelay\=[1,2,3,4,5,6,7,8,9] sierra-heartbeat-log-lag-issue.txt Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=11, NumberOfOutstandingSendBuffers=26, TransmissionDelayInMilliseconds=730, ServerSendBufferSizeInBytes=228347, ActualMessageDelay=97.2 seconds, DataCompRatio=3.37, UncompressedBytes=3111607, CompressionTime=0.022389(secs), NumCompressions=387, Source=10.10.20.111, MaxSendBufferSize=257797, MaxSendBufferSizeDateTime=2023-10-24 16:47:23 | 2023-10-24 12:49:00.402 Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=11, NumberOfOutstandingSendBuffers=45, TransmissionDelayInMilliseconds=1205, ServerSendBufferSizeInBytes=490198, ActualMessageDelay=2.4 minutes, DataCompRatio=3.36, UncompressedBytes=4002710, CompressionTime=0.027607(secs), NumCompressions=407, Source=10.10.20.111, MaxSendBufferSize=522594, MaxSendBufferSizeDateTime=2023-10-24 16:47:42 | 2023-10-24 12:50:06.012 Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=10, NumberOfOutstandingSendBuffers=56, TransmissionDelayInMilliseconds=1480, ServerSendBufferSizeInBytes=780357, ActualMessageDelay=3.6 minutes, DataCompRatio=3.35, UncompressedBytes=4850271, CompressionTime=0.031718(secs), NumCompressions=421, Source=10.10.20.111, MaxSendBufferSize=780357, MaxSendBufferSizeDateTime=2023-10-24 16:48:03 | 2023-10-24 12:51:38.288 Denali Data Feed (Market Orders Data) | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=4, NumberOfOutstandingSendBuffers=10, TransmissionDelayInMilliseconds=330, ServerSendBufferSizeInBytes=44158, ActualMessageDelay=6.2 seconds, DataCompRatio=3.14, UncompressedBytes=137741, CompressionTime=0.000812(secs), NumCompressions=13, Source=10.10.20.123, MaxSendBufferSize=123986, MaxSendBufferSizeDateTime=2023-10-24 16:52:29 | 2023-10-24 12:52:38.115 Denali Data Feed | Heartbeat from server , ServerReceivedClientHeartbeatSecondsAgo=5, NumberOfOutstandingSendBuffers=22, TransmissionDelayInMilliseconds=630, ServerSendBufferSizeInBytes=197139, ActualMessageDelay=20.0 seconds, DataCompRatio=3.33, UncompressedBytes=1355423, CompressionTime=0.009671(secs), NumCompressions=100, Source=10.10.20.123, MaxSendBufferSize=239768, MaxSendBufferSizeDateTime=2023-10-24 16:52:51 | 2023-10-24 12:53:11.946 00, Source=10.10.20.123, MaxSendBufferSize=239768, MaxSendBufferSizeDateTime=2023-10-24 16:52:51 | 2023-10-24 12:53:11.946 |
| [2023-10-25 16:01:32] |
| Sierra_Chart Engineering - Posts: 17182 |
|
If these other delays were in the log, we checked again and did not see them, then we had not noticed them. We do look at a lot of information and cannot notice everything. Anyway, this is simply due to network connectivity. We have no control over that. Apparently there was some, connectivity issue somewhere. Sierra Chart systems are not the cause at all of this. There was never a problem on the Sierra Chart side related to this. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-10-25 16:06:09
|
| [2023-10-25 16:08:04] |
| Sierra_Chart Engineering - Posts: 17182 |
|
Also for the record those types of lags are very very severe. There was absolutely definitively Internet connectivity issue somewhere. This is definitively not at all on the Sierra Chart side. Never was. Whatever users were experiencing a lag, that was due to network connectivity completely separate from Sierra Chart. And actually we did see the larger lags, in the log that you gave. We finally saw them. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-10-25 17:16:50
|
| [2023-10-27 14:59:09] |
| PeteB - Posts: 17 |
|
Thanks for the replies. What is the best way to trace the network to find where the delays are occurring? By removing denali from the mix, the lags disappeared, which led me to indict denali. This is not a comprehensive way though to find lags, so how could I better diagnose this in the future? Thanks.
|
| [2023-11-01 15:19:04] |
| PeteB - Posts: 17 |
|
yep
|
| [2023-11-01 19:50:13] |
| Sierra_Chart Engineering - Posts: 17182 |
|
We will see if we can do this for you.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: