Login Page - Create Account

Support Board


Date/Time: Sat, 04 May 2024 20:13:29 +0000



Significant Lag past version 1958

View Count: 2865

[2019-08-01 15:00:34]
User379468 - Posts: 508
Got a SC UI freeze in 1966, only 3 charts open, global update set to 900ms, 2 charts set to 100ms, SC CPU use around 7%. Charts continued updating fine, but no control bar or main window or file menu access or response, required task manager process kill.
[2019-08-01 18:34:25]
Sierra Chart Engineering - Posts: 104368
In regards to post #50, thank you for the feedback. 1966 uses a much more advanced method of managing the Chart Update Interval. After how long of a time did this occur?

Anyway we know how to resolve that. We think we know where the problem is.

There is a running average made to determine the Chart Update Interval but it will need to adjust itself quickly.
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, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2019-08-01 18:38:29]
User379468 - Posts: 508
After a short time, maybe less than 5 minutes or so.
[2019-08-01 19:24:06]
Sierra Chart Engineering - Posts: 104368
Ok thank you for the information. We will have a new release out later today which we expect will finally resolve this.

Also 1964 the current release, just uses the standard method of updating which is not affected by the changes.
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, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
[2019-08-02 01:57:37]
101010 - Posts: 18
Could support outline in detail how to optimize the Chart Update Interval to find the lowest/optimal setting?

My machine has an i7-8750H CPU @ 2.20 GHz and listed as 6 cores with 12 logical processors. So approximately what % of CPU should Sierra be using? Is the max per core 100/6 so 16.7% essentially? And if so what % of CPU is considered high and what is considered acceptable in this case?

I notice with higher Chart Update Intervals I'm missing upticks/downticks on the DOM that are otherwise visible with a lower setting. If Sierra is running responsively with a low Chart Update Interval but has a higher CPU %, but the DOM has noticeably more speed visually is there any harm in running the lower interval? I know you've covered this information rather extensively, but I'm just looking for some clarification. Thanks.
Date Time Of Last Edit: 2019-08-02 02:16:37
[2019-08-02 03:07:20]
Sierra Chart Engineering - Posts: 104368
With 12 logical processors the primary thread of Sierra Chart can use up to 8.33%. If you see the CPU usage hitting the maximum often, then the chart update interval is too low.

The proper solution is to follow the instructions here:
Overview of Trading: Sierra Chart Configuration for Most Low Response Time Trading

Also version 1967 uses the older method of updating until we work out a proper solution to updating charts under the new more efficient method.
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, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2019-08-02 03:07:54
[2019-08-02 04:27:45]
101010 - Posts: 18
How are these CPU % numbers affected by the chip's boost speed? For instance, my chip's base speed is 2.20 GHz but at the moment is running at 3.90 GHz and Sierra usage is hitting 16%. The program is perfectly responsive and I'm only running 3 charts in the main instance. Total CPU usage is 29%. Does this still imply I will need to lower my chart update interval or would experience delays sending live orders? Sorry for the repeated questions, but I am trying to gain a better understanding of how this functions as a whole. Thanks!
[2019-08-02 04:31:37]
Sierra Chart Engineering - Posts: 104368
They are not affected by that all. Really you are going to be in the best position to set the Chart Update Interval based on your own testing. We cannot answer that. What we will say is that using lower than 100 milliseconds does not make sense.
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, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2019-08-02 04:32:11
[2019-08-04 20:11:25]
User379468 - Posts: 508
Really you are going to be in the best position to set the Chart Update Interval based on your own testing.

Can you help give your users a reliable/practical tool to easily use like the ideas suggested below to do this without guessing?

In light of this discussion it would be nice to have some sort of floating window that will show list of all charts and their refresh time all at once. Perhaps some extra symbol showing enforced extra delay would be nice too.

Other option to show this information could be CW menu, right beside window title

Is there a way to display in the platform or each chart any delay/overlap occurring or what the dynamic interval adjustment is doing so users can fine tune the correct update interval for their needs?

[2019-10-31 20:59:08]
User379468 - Posts: 508
SC Engineering:

1. Can you comment on Post #58?

2. What was the final implementation of these changes to how chart update intervals are managed?
[2019-11-01 13:01:07]
Sierra Chart Engineering - Posts: 104368
What we will say, is we did not get back to the updated method of chart updating so it remains like it has always been in the past.
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, *change* to 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