Support Board
Date/Time: Fri, 14 Mar 2025 15:21:10 +0000
2714 - 400ms update 'fix' - does not fix lag
View Count: 238
| [2024-12-03 11:30:23] |
| User677437 - Posts: 57 |
|
Some of us run heavy duty charts with detached windows, market profiles, volume profiles, numbered bar studies etc, you guys know how complex things can get from our end. We are experiencing an unusable lag with these SC timer update versions. You have to know that we are not exaggerating on the performance issues. There is significant lag and unresponsiveness on my sub instances, which makes it unusuable. I can't move charts on 2 instances, can't move the title window bar. Main instance with just doms looks ok I can move those window. I'm using detached windows. You guys say you have no problems running thousands of symbols, and over 20 instances, that's fine but what studies are you running on those charts. We know that it is possible for chart/study/data settings where something can brick a whole chartbook/instance on an update or by user error. A team of traders running some heavy duty charts would be great to beta test these updates. |
| [2024-12-03 13:11:37] |
| Sierra_Chart Engineering - Posts: 18784 |
|
What do you mean by 400 ms in the subject? Still the issue, is your Chart Update interval, is too low either globally, or in some charts, and based upon the chart configuration and computing power of the computer it cannot handle it. We will make additional changes to automatically increase this. But we want to know what you mean by 400 ms. 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-12-03 13:13:06
|
| [2024-12-03 14:20:37] |
| User677437 - Posts: 57 |
|
Referencing the Chart Update Interval In Milliseconds. My mistake, Come to think of it this could have been the last setting I tried yesterday. I thought I read something about a default time being added to this version. 400 was no good for me. 1000ms got better but a whole instance wasn't responding. I went to 2000ms on 4 instances, with my main instance being for doms at the lowest setting of 10ms. I run many detached windows. Every user is going to have to tune this update interval to adding or subtracting charts / studies from an instance, and distributing charts to other instances. So previously before hand if someone had heavy duty chartbooks with dozens of charts and detached windows, and they werent' distributing load properly because they want global crosshair or attached doms to charts etc - there was no way they were getting 10ms update intervals. And you guys have been clear on what to do for properly optimizing performance - however before the timers the chart functionality still worked even when it was functioning at a much slower speed than what was set on global, it still responded to cursor inputs, scrolling, moving charts around etc, rather than getting a frozen program. And probably most importantly chart and dom speed was synchronized on large chartbooks that weren't distributed over instances. Now people have to find the real update speed that their chartbook configuration / instances allows them to get. or else they will have an unusable program depending on how built out their charts are. Granted I'm an outlier on how many charts and studies I'm running for es, nq, cl, gc, bonds. I got the screens for it. So 2000ms is my number. If there are nq traders running heavy chartbooks, they will have to compromise and get used to split global crosshair on an execution instance with or without chart, in order for it to be as close to updating interval time as a DOM. And the mismatch in speeds between the dom and the scalping chart with alot of studies on it, in this new optimized instance can be a bit of a problem for them. before the timers and distributing load, all price was synchornized between charts in a chartbook. DOM based traders respond to the speed of the price on the ladder and having to use a slower moving reference chart is going to be a hard mental change. And the way it is set up now, they need to tune a scalp chart update speed, find that and then synchro the dom with that speed. Date Time Of Last Edit: 2024-12-03 14:23:15
|
To post a message in this thread, you need to log in with your Sierra Chart account: