Login Page - Create Account

Support Board


Date/Time: Sun, 05 May 2024 18:26:03 +0000



Problems with Denali Data Feed

View Count: 592

[2024-02-08 18:53:44]
User330437 - Posts: 7
Dear Sierra Chart support,

i have a servere Problem with the Deanali Data Feed for CME. It is extremely laggy and serverly slower than my CQG Data Feed i pay for as well. If i use the Deanli Data Feed it is literally impossible for me to trade, so i went back to using the older Versions of Sierra Chart so i can still use CQG, but i really want to switch to the Teton Order Routing service, so i have to get my Denali Data Feed into working order. i have tried everything i could, my Internet connection is very good ans stable, i tried to ping the Sierra Cahrt Servers and it shows no packet loss, but it is still laggy compared to other Data Feeds. Pls help me i am all out of ideas (i even tried to switch to linux to see if that fixes my Problem).
Thank you for your help,
Thomas
[2024-02-08 19:17:54]
John - SC Support - Posts: 31379
The main things to look at are listed at the following link:
High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often

In addition to the above, we would like to see your Message Log to ensure there is not something else occurring. Please get us your Message Log by following these instructions:
Support Board Posting Information: How to Post Your Message Log (Required In Some Cases)
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-02-08 19:43:08]
User330437 - Posts: 7
i have tried all the things i have found on your support forums, but sadly none work. my cpu usage is at 3-4% and the settings in my sierra chart work fine when i use version 2350 with cqg data, only the denali feed lags. i tried playing around with every single setting in the software for the last 4-5 mounths, but i cant fix it myself.

i have send my message log for review
[2024-02-08 19:46:33]
John - SC Support - Posts: 31379
There is one big problem we see from your log. You have the setting for "Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Chart Data Feeds" set to "No".

You need to change this to "Yes" and then select OK to close that window, then select "File >> Reconnect". After that, let us know how things are going.

We will say though, we are surprised you were getting data at all, you should not have been.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-02-08 19:53:53]
User330437 - Posts: 7
i already switched the seting back to yes. i just turned it of to make sure the data is still fine with cqg at version 2350 before i wrote the support ticket. i have already switched back to version 2598 an turend to switched the allow sierra cahrt data back on .
[2024-02-08 19:59:17]
User330437 - Posts: 7
i have recorded a video where you can see the difference in speed beetween my cqg data feed and my denali feed. if you want i can provide it for you
[2024-02-08 21:09:39]
John - SC Support - Posts: 31379
The Message Log you provided does not give us the information we would need given what you have stated above.

Please follow these instructions to get us your log:

Follow the instructions here to clear the Message Log:
Message Log: Clearing the Message Log

Close all of the Chartbooks with "File >> Close All Chartbooks".

Open a single chart for the symbol you have an issue with through "File >> Find Symbol". Tell us that symbol of the chart. Tell us about *one* symbol only.

Disconnect from the data feed with "File >> Disconnect".

Connect to the data feed with "File >> Connect to Data Feed".

After the connection and after about 1 minute, provide a copy of the Message Log following these instructions:
Support Board Posting Information: How to Post Your Message Log (Required In Some Cases)

We will then determine what the problem is.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-02-09 07:52:32]
User330437 - Posts: 7
i have sent you the requested mesage log, thank you for your help
The symbol is ESH24.
Date Time Of Last Edit: 2024-02-09 07:53:54
[2024-02-09 09:20:35]
User330437 - Posts: 7
is there a way to chose the server i get my real time data from? i pinged all the data servers from this list (Data/Trading Service Connection and Symbol Issues: IP Addresses) and ds30.sierracharts.com shows the best latency and no packet loss, while some others show up to 15% packet loss. i found the CME exchange data feed server adress and port override setting, but i dont know if its the setting i am looking for and how to use it.
[2024-02-09 15:29:03]
John - SC Support - Posts: 31379
There is nothing in the log that shows any issues, so it doesn't look like a major connectivity issue.

There is not a way for you change which server you connect to. But, if you look at your log, you can see which server you are using, then if you select "File >> Reconnect" you will then be connected to a different server, so you can do this to connect to the specific one you want.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-02-09 16:14:02]
nosast - Posts: 290
User330437:
are you also based in Europe? I have the same issues going on for months with Denali and switched to Rithmic until this gets solved for good. I tried everything and also different internet providers with no luck and currently thinking that it's caused by backbone-routing. Next step I'm trying is to get a VPS next to CHI and execute via remote desktop.

Teton and Rithmic for example are rocksolid. Attached are screenshots from a few minutes ago when Nasdaq broke 18k.
Date Time Of Last Edit: 2024-02-09 16:32:34
imageSNAG_ 2024-02-09 - 17-06-00.png / V - Attached On 2024-02-09 16:13:19 UTC - Size: 31.96 KB - 74 views
imageSNAG_ 2024-02-09 - 17-10-14.png / V - Attached On 2024-02-09 16:13:22 UTC - Size: 76.23 KB - 59 views
imageSNAG_ 2024-02-09 - 17-09-47.png / V - Attached On 2024-02-09 16:13:38 UTC - Size: 73.15 KB - 57 views
[2024-02-11 04:44:10]
Sierra_Chart Engineering - Posts: 14234
Yes they are in Europe.

That IP address that starts with 64.125 that you are associating with Teton is not ours.

For more information about the issue, refer to:
Infrastructure Upgrades
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
[2024-02-11 04:45:53]
Sierra_Chart Engineering - Posts: 14234
Do not change this:
CME exchange data feed server adress and port override setting.

Instead refer to:
Infrastructure Upgrades
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: 2024-02-11 04:46:05
[2024-02-11 13:06:20]
nosast - Posts: 290
That IP address that starts with 64.125 that you are associating with Teton is not ours.

I know but that is the last hop that answers to ping packets for my monitoring.
[2024-02-11 13:21:24]
nosast - Posts: 290
Attached is a traceroute from Germany. Shows the same like the example you mentioned from Portutal. It looks like a peering issue with Cogent or any other carrier involved in the route. Thanks for getting this sorted out - really looking forward to be able to trace the route back from Chicago to my location to see the full picture.

Hop Sent PL% Min Max Avg Host Name / [IP]
1 453 0 2.05 40.83 5.32 fritz.box [192.168.1.1]
2 453 0 5.51 78.89 11.15 p3e9bf597.dip0.t-ipconnect.de [62.155.245.151]
3 453 0 10.80 341.82 37.05 f-ed12-i.f.de.net.dtag.de [217.5.94.226]
4 453 1 10.08 92.89 15.38 80.150.170.131 [80.150.170.131]
5 453 3 10.70 95.85 17.05 be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118]
6 453 0 17.48 122.13 24.28 be2814.ccr42.ams03.atlas.cogentco.com [130.117.0.141]
7 453 0 115.81 228.63 122.04 be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41]
8 453 0 122.15 187.65 125.90 be3488.ccr52.lhr01.atlas.cogentco.com [154.54.60.14]
9 453 0 119.70 179.69 124.85 be4325.ccr42.jfk02.atlas.cogentco.com [154.54.93.13]
10 453 0 122.06 191.65 126.58 be2890.ccr22.cle04.atlas.cogentco.com [154.54.82.245]
11 453 0 119.58 227.69 126.43 be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
12 453 0 119.98 178.02 123.78 be2248.ccr22.ord03.atlas.cogentco.com [154.54.5.158]
13 453 0 123.05 182.11 127.24 be2860.agr61.ord03.atlas.cogentco.com [154.54.87.62]
14 453 9 118.69 178.10 123.09 38.103.112.197 [38.103.112.197]
Date Time Of Last Edit: 2024-02-11 13:26:37
imageScreenshot 2024-02-11 at 14.15.53.png / V - Attached On 2024-02-11 13:19:33 UTC - Size: 647.37 KB - 45 views
[2024-02-12 15:44:53]
User330437 - Posts: 7
Thank you very much for your help. I am really looking forward to being able to finally use Teton.
Date Time Of Last Edit: 2024-02-12 17:16:33
[2024-04-17 21:32:45]
nosast - Posts: 290
@Sierra_Chart Engineering

Since a few days the peering issues with Cogent from/to Europe got worse again. After around 1pm central time Denali is way to laggy and stuttering. My monitoring shows lots of paketloss.

Is there any news regarding the DC switch to Michigan and the feature to trace from DC to the users IP? (my ISP needs this to let me open support tickets). I would really love if you also use another carrier for the main connection. Cogent caused the issues some users had in February as they withdrew peering with NTT.

wikipedia states:
In February 2024, Cogent withdrew peering with NTT in Europe,[33][34] forcing all their peering traffic to go through their common remaining interconnections in USA, increasing latency and traffic loss between both networks, to complain against refusal of peering settlements in Asia from NTT.
https://en.wikipedia.org/wiki/Cogent_Communications#Peering_disputes
Date Time Of Last Edit: 2024-04-18 20:35:45
[2024-04-17 22:09:11]
Sierra_Chart Engineering - Posts: 14234
Allow about four more weeks, before another ISP is added. We are getting very close to doing that.

And we will bring this posting to the new ISP they can comment on it.
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
[2024-04-17 23:06:46]
Sierra_Chart Engineering - Posts: 14234
The move to Michigan will be completed in about two months:
Is there any news regarding the DC switch to Michigan and the feature to trace from DC to the users IP?

We had other higher priorities affecting, adding the trace route functionality.
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:

Login

Login Page - Create Account