Support Board
Date/Time: Fri, 04 Jul 2025 15:45:13 +0000
2702 - orderflow not smooth
View Count: 450
| [2024-11-07 21:37:23] |
| nosast - Posts: 313 |
|
I'm seeing very stuttering orderflow (NQ) with 2702. Being aware of the changes regarding timer events I did go up from my chart update interval of 75 ms to 750 ms (just for testing) and still orderlow just stops for half a second and then bursts before the next stutter. Went back to 2700 with a 75ms update interval and have no issues. Chart drawing load is handled by nvidia GPU (OpenGL) to minimize CPU load. Are these timers also utilized for orderflow from Denali somehow? I have compression very low (standard with 5ms) so maybe that could be related? Any suggestions on how to get the most accurate update in charts and orderflow with least amount of lag for a scalper? Maybe you could consider an option to keep the old timers for the next couple of versions? Date Time Of Last Edit: 2024-11-07 21:56:43
|
| [2024-11-07 22:59:06] |
| Sierra_Chart Engineering - Posts: 20080 |
|
First of all we do not know what is meant by order flow, we assume you just simply are referring to the data feed. If you notice Sierra Chart is less responsive or the data feed is less responsive, with this version and higher our recommendation is to use a higher global Chart Update Interval like 800 ms or higher or even higher. And only those charts which you want to update very fast, specify a lower Chart Update Interval on those. Specify a chart specific Chart Update Interval of 0 on other charts. So you reduce the updating load. Additionally, refer to: Chart Trading and the Chart DOM: Improving Performance Of Chart / Trade DOM You can also try using our server in Germany and see if that helps in your case: ds14-2.sierracharts.com Refer to this setting: Sierra Chart Server Settings: CME Exchange Data Feed Server Address and Port Override (Global Settings >> Sierra Chart Server Settings >> General >> Special) The data feed, is delivered through a network socket connection and events and that does not involve Windows operating system timers. There are no changes 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: 2024-11-07 23:00:41
|
| [2024-11-08 00:56:37] |
| nosast - Posts: 313 |
|
Thanks - I will try to test again 2702 and compare it to 2700 side by side. Sierra chart is very responsive - it was just how transactions/orders from the feed are flowing in and being visible on the chart. Testing with a higher update interval did not really change this behavior and for live trading I could never go to 800ms interval on my execution chart and market depth chart. All other charts are 500ms and 1000ms. |
| [2024-11-08 01:54:24] |
| Sierra_Chart Engineering - Posts: 20080 |
|
I could never go to 800ms interval on my execution chart and market depth chart. Yes we understand, on these charts you can use a much lower number.
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-11-08 10:11:40] |
| nosast - Posts: 313 |
|
Did some testing with 2703 and CPU chart drawing (OpenGL=off). Interface is completely frozen and one CPU core gets overblown and clock frequency is maxed out. With OpenGL it is better but not as good as 2700. So for my use case and PC I will stick with 2700 and OpenGL for now. Interface is snappy and drawing load is handled by GPU while CPU is hovering around 7-12 % load. Seems like the best combination altough OpenGL interface looks a bit more basic. |
| [2024-11-08 14:20:14] |
| Sierra_Chart Engineering - Posts: 20080 |
|
This is not a performance issue within Sierra Chart . There are no changes which cause any worse performance. None at all. The issue is simply that you are using too low of a Chart Update Interval with too many different charts.
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-11-08 14:20:33
|
| [2024-11-08 14:30:24] |
| User628480 - Posts: 114 |
|
This is not a performance issue within Sierra Chart . There are no changes which cause any worse performance. None at all. The issue is simply that you are using too low of a Chart Update Interval with too many different charts.
Do you have recommendations for converting existing chart interval settings to the new timer values? Example. If current global setting is 500 and DOM is set to 10 and other charts are set to 40... What would the new settings be for a starting point? |
| [2024-11-08 14:55:48] |
| Rui S - Posts: 200 |
|
Do you have recommendations for converting existing chart interval settings to the new timer values? Example. If current global setting is 500 and DOM is set to 10 and other charts are set to 40... What would the new settings be for a starting point?
I think the best you can do is to start trying one value at a time, until you reach the best balance possible. It is not possible to give you a kind of a conversion ratio for this, because it depends on several things (e.g. your PC, your charts and studies, etc.) |
To post a message in this thread, you need to log in with your Sierra Chart account: