Login Page - Create Account

Support Board


Date/Time: Tue, 09 Sep 2025 23:23:05 +0000



Issues with v2712 vs v2700

View Count: 388

[2024-12-02 18:13:20]
User719512 - Posts: 321
Experienced unresponsive and lagging issues with v2712 with chartbooks that worked perfectly on v2700.

I see in other threads that you believe this should not be happening, but many others and I are in fact experiencing issues and the only thing that changed was the version of Sierra.

A friend sent me a chartbook with such issues and I saw hangs while I translated symbols and data was loading. After a long long wait, the chart did respond, but very slowly. I noticed 3 of his charts had 40, 60 and 60 update times.

Q1: How would this impact your new timer models where an existing/old chart with perhaps existing update values that might be too low for the new timer model work when opened for the first time?

Q2: This is not new, but something to consider, and something that the Windows message pump also tries to alleviate, is ensuring the UI, menus, etc. remain responsive even if some other parts of the app are not.

Observation:
Things seem to be a lot worse while data is downloading and refreshing. As a test, click once and hover over the Sierra menus while a chart is loading and move the mouse over the main menu names to see the menus display and change as the mouse is moved. While existent in v2700, the unresponsiveness of these actions seems works in v2712.

Q3: related to Q1, can someone get into a spot where if they set the global chart update interval too low, or set individual chart intervals too low that all of Sierra becomes less responsive because some charts are now hogging all the resource and cause some unintended side effects? Same question for opening an older chartbook that has too aggressive update intervals. Will Sierra detect this and/or ensure all charts, and the Sierra UI get cycles and not get starved by other charts?

Other:
While doing some testing with v2712, I got into some state once where all of Sierra froze and it also caused every other Windows apps to hang, and I could not alt-tab switch to them or bring them to the front with the mouse. This seems to indicate that Sierra was somehow blocking the Windows message pump. Once I terminated Sierra, my system went back to normal.

Summary:
I cannot explain a reason everything that I experienced, or track down the exact cause, but like others, things that worked last week are not working now.
[2024-12-02 18:17:33]
John - SC Support - Posts: 41709
Q1. Version 2713 has an option that when a Chartbook is opened in "Safe Mode" the Chart Update Interval is changed to 750 ms. This will allow the chart to be opened and modified and the Chart Update Interval can be lowered down to something that works best for that chart.

Q2. This is handled as best we can at the moment.

Q3. See response to Q1 above.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-12-02 18:31:42]
User719512 - Posts: 321
Hi John, thanks for the reply. I know you all are looking into all these things. You should add your Q1 answer to the What's New for v2713. Even with this documented there, I would guess many people will not know/discover this, nor realize that they are in such a predicament (especially if opening an older chart).

Ideally, Sierra would detect this and post an alert/message that a chart cannot support the specified update time. Possibly auto-increasing the chart update time or something so an offending chart does not take down the whole thing...

How will this work if a given update time is fine 90% of the time, but other apps opening, loading, refreshing, put load on the system? Will Sierra just be slow (as expected I presume), but still WORK overall? Thinking the experience for short durations when cancelling/flattening a trade for example...will Sierra always be responsive to get the message, even with a mild delay?
[2024-12-02 19:51:10]
John - SC Support - Posts: 41709
Hi John, thanks for the reply. I know you all are looking into all these things. You should add your Q1 answer to the What's New for v2713. Even with this documented there, I would guess many people will not know/discover this, nor realize that they are in such a predicament (especially if opening an older chart).

It is coming, the release was just put out this morning.

Ideally, Sierra would detect this and post an alert/message that a chart cannot support the specified update time. Possibly auto-increasing the chart update time or something so an offending chart does not take down the whole thing..

We do not see issues when we use a lower Chart Update Interval, so we do not think that detecting a particular value would be a solution.

How will this work if a given update time is fine 90% of the time, but other apps opening, loading, refreshing, put load on the system? Will Sierra just be slow (as expected I presume), but still WORK overall? Thinking the experience for short durations when cancelling/flattening a trade for example...will Sierra always be responsive to get the message, even with a mild delay?

There should not be any differences in how the software works now versus previously. We work hard to keep Sierra Chart as lean as possible so that system resources are available to do what needs to be done. If you worry about other apps causing issues with the responsiveness of your system, then we recommend using a computer to run Sierra Chart where you do not use any other applications.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-12-02 21:21:35]
Sierra_Chart Engineering - Posts: 20857

Ideally, Sierra would detect this and post an alert/message that a chart cannot support the specified update time. Possibly auto-increasing the chart update time or something so an offending chart does not take down the whole thing...
Yes we observe no problem and Sierra Chart automatically ensures that the interval between updates, is at least what you have set for the Chart Update Interval. So if you have set 50 ms that means there will be a 50 ms pause before the next update of a particular chart.
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