Support Board
Date/Time: Wed, 05 Feb 2025 20:07:34 +0000
Heavy User 2716 Test - 100+ Detached Windows 1500ms Global *Chart* Update Time Works
View Count: 238
| [2024-12-04 06:23:32] |
| User677437 - Posts: 49 |
|
From the sticky " Update: When we explain about using too low of a Chart Update Interval, we are referring to using intervals, in particular under 50 ms and using this for a lot of charts. Using for example 10 or 20 ms and using this on a lot of charts. We are not implying, that you need to be increasing the global chart update interval to 1000 ms or 2000 ms or 5000 ms. It is using 10 ms on a large number of charts. The thing is we are using ourselves a global 10 ms update interval and not observing any issue. " Per title. I do not use integrated chart DOMS. My DOMS are on a stand alone instance. I have 100+ detached windows across sub instances, with 1 main instance running 6 doms and 4 sub instances. My main instance doms have 250ms global update interval and all my sub instances have 1500ms global update interval with 2000ms timer maximum delay. The timer management chart calculation draw time is set to its default value of 3. I should make the distinction that I am running A LOT of studies on my charts which is without a doubt going to effect things. Right now I am seeing ___3,200MB____ of ram usage for Sierra charts. This is about typical but I don't have an exact reference point before the this. I can install back to a later version and find out. An interesting poll to have would be - how many mbs is someone's set up. There is no longer a function to change specific chart update intervals to over-ride the global settings in chart settings > performance. * Any changes going below 1500ms for my sub instances - the charts are laggy with cursor movement, and functionality with left clicking, drawing etc, title bar movement - all the stuff that people have mentioned. I am not making more instances, I want all these charts together in relative markets for the use of the global crosshair. This is a key reason why people like to build out large chart books with detached windows. The ceiling is very high and is a key feature of this platform over other providers. As many charts, profiles, footprints/ numbered bars/ as you want and the program won't break like how Ninja Trader performs or other web UI programs. We understand how much of an improvement you guys are seeing since this function has been 'abused' for years with a + 90% drop rate, because we just didn't know better. You guys have always told people how to optimize the platform. And how orders are processed. High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often: 30.44 - Performance Differences Between Versions of Sierra Chart Do people do it ? ... Some don't. And that's why SC has a specific demographic of users, using other software providers for high latency doms - because they like the feel / speed of it, and they use SC just for charting or footprints/numbered bars. The SC timers are going to be a fork in the road regarding these traders. Either they stay with their charts and doms at the same speed that they have always been, before the SC timer fix OR they will have to ADAPT to a faster moving DOM that is not synchronized to their reference chart. For instance for me, putting my scalping chart into the the main instance that is running 6 doms and now 1 nq scalp chart. The NQ scalp chart * running many studies * will not keep up with the DOM. And this isolates the global crosshair from the rest of my NQ charts. Because of these timers - it's going to make SC even higher of a learning curve when you have to go through the entire optimization section and before that wasn't the case, you still could use the chart functionality even when it had decreased performance. You still could trade and chart for Heavy Users. This is going to cause - the heavy users - to have to optimize their chartbooks with DOMS and Footprint charts on their own instances and not attached to chartbooks that have all the multi timeframe analysis / equities / internals etc. If people with moderate built out chartbooks are doing good on 50ms, 100ms, 250ms or 500ms global update interval than that needs to be within the recommendations. This could be done via SC ram usage and number of instances poll. We need users to share live results. You guys have the data on how many traders are ES / NQ traders. And because those are 'the' markets, and because global crosshair only works on one instance this has been and is going to be a problem in distributing load, and now to find the right compromise on ms global update interval for how many chartbooks/ charts/ studies they are using in a single instance. Global crosshair on multiple instances or being able to select instances, or the specific chart or chartbook on an instance ( If it is possible ), will get traders to distribute load properly. As an example - I want to see where NVDA lower timeframe and higher timeframe charts are to my NQ scalp chart, next to my NQ footprint, next to NQ daily, weekly, monthly tpos. And then I want to compare where my nq charts are to my ES chart versions of those types. Date Time Of Last Edit: 2024-12-04 06:33:09
|
| [2024-12-04 06:52:21] |
| Sierra_Chart Engineering - Posts: 18293 |
|
Nothing has changed with this: There is no longer a function to change specific chart update intervals to over-ride the global settings in chart settings > performance. The chart specific Chart Update Interval is in Chart >> Chart Settings >> Display This is not true in 2716 because the timers are automatically managed: Because of these timers - it's going to make SC even higher of a learning curve when you have to go through the entire optimization section and before that wasn't the case, you still could use the chart functionality even when it had decreased performance. You still could trade and chart for Heavy Users. Honestly, all of this post is very bewildering to us. There is no performance degradation and no issues, with the new timer functionality in particular with 2716. It is the opposite. You should be having very good performance, and very fast updating. Help topic 30 is identifying various things that could be going on which is causing an excessive load. It is not something that usually needs to be looked at. 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-04 06:58:05
|
To post a message in this thread, you need to log in with your Sierra Chart account: