Support Board
Date/Time: Fri, 13 Jun 2025 09:21:50 +0000
[Locked] - Denali lagging today after FOMC?
View Count: 643
| [2022-11-02 19:36:07] |
| tomas262 - Posts: 148 |
|
occasionally the feed pauses for a while. see the clip symbol M2K (denali) comparing to RTY (Gain cap) Date Time Of Last Edit: 2022-11-02 19:37:03
|
 denali.mp4 - Attached On 2022-11-02 19:35:53 UTC - Size: 2.18 MB - 307 views |
| [2022-11-02 19:49:04] |
| Rui S - Posts: 200 |
|
Yes, it was lagging. Actually, it has really stopped at least two times - 2:41:27 and 2:51:22. I had to disconnect and reconnect to get it running again. SC Support is improving the system and hopefully it will be fine by the end of the week. Important Notice: Denali Data Feed Infrastructure Updates |
| [2022-11-02 21:11:02] |
| AD544 - Posts: 64 |
|
SC Support is improving the system and hopefully it will be fine by the end of the week.
I hope... since AMP told me they are very close to support Teton I stopped using Sierra when they stopped to fully support CQG I am planning to come back to Sierra, probably the best software around These kind of things should not happen Date Time Of Last Edit: 2022-11-02 21:13:03
|
| [2022-11-03 06:06:02] |
| Sierra_Chart Engineering - Posts: 19909 |
|
We actually were aware of this at the times it was happening. The issue was not on our side directly. We have multiple Internet connections. The problem affected just one Internet connection out of many and only the users that were on that Internet connection. So this is 1 out of 5 Internet connections being used. So 20% of the users would have been affected. This was an Internet connection issue. There were no problems, with the processing of the CME data and delivering it to users. It was an ISP issue. Although this ISP, was one of the ISPs being used. The problem was reported to the data center in the evening. We will see what they say about it. And if they are not recognizing the problem and implementing a solution, we will need to use a different Internet connection. Because this was completely unacceptable behavior of that connection. Hopefully they will be able to resolve it because it looked as though it was affecting just one of their core routers and not the other one. We have two Internet connections in the data center, each one going through a different core router of the data center, and only one of them was affected. The other one did not exhibit this behavior at all. There was more than enough capacity available on that Internet connection even with the increased market activity. So it was not a capacity issue on our side. In this case reconnecting to the data feed would have resolved the problem since you would have been connected to a different server. Teton order routing was not at all affected by this issue. It was just one Internet connection used for market data only. And as we said this was not an issue directly on our side. It was an ISP issue. Teton order routing runs on a completely different network and data center, and has two different Internet connections. We were increasing it to 3 connections. 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: 2022-11-03 09:17:30
|
| [2022-11-03 11:24:52] |
| Rui S - Posts: 200 |
|
Teton order routing was not at all affected by this issue.
Well, I am a Teton user and it didn't help me anyway when the data feed froze. I had to check on a secondary data feed if it was an exchange problem or a Denali problem. Fortunately for me, I had no open positions nor pending orders at those times, but I had a few seconds before. It's quite scary. As always, I trust you will find the best solutions for these data problems we have been experiencing lately. |
To post a message in this thread, you need to log in with your Sierra Chart account: