Support Board
Date/Time: Sat, 05 Apr 2025 00:56:47 +0000
Kiwi Resync Study - Memory leak?
View Count: 4520
| [2019-03-20 00:36:22] |
| Willson - Posts: 176 |
|
Sending a forbidden BIG thankyou to Kiwi, sstfrederik,user212764 all that helped a lame programmer thru this. It now works
|
| [2019-08-02 10:15:20] |
| samual sprat - Posts: 343 |
|
You can use the 'Chart Recalculation - Periodic' study instead, does the same thing and it's built into sierra now
|
| [2019-08-26 21:31:50] |
| User132748 - Posts: 159 |
|
Dear SC, Chart Recalculation - Periodic study causes 100% CPU load, I guess because theres sc.UpdateAlways=1 inside code. Is this really needed? I guess it should be ok to do time calculation at standard chart updates? Thanks |
| [2019-08-27 17:57:37] |
| |
|
If it causes that kind of a load, increase the Recalculation Time in Seconds for that study and also the Chart Update Interval: Chart Settings: Chart Update Interval in Milliseconds (Chart >> Chart Settings >> Display >> Chart Update Interval menu) And refer to help topic 30: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often We will also add an option for that study to control whether it Updates Always. 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-27 18:04:31
|
| [2025-04-02 05:16:17] |
| User35525 - Posts: 184 |
|
The built-in 'Chart Recalculation - Periodic' study causes a constant CPU load. Is this necessary or can it be adjusted to just run on bar-end like this study suggests? Recalculate on Bar Close. Any options? SCSFExport scsf_study_name(SCStudyGraphRef sc) // scsf_Name can be anything { if(sc.GetBarHasClosedStatus()==BHCS_BAR_HAS_NOT_CLOSED) return;//do not do any processing if the bar at our current index has not closed if (sc.SetDefaults != 1 && sc.IsFullRecalculation != 1) { sc.FlagToReloadChartData= 1; } else { sc.FlagToReloadChartData= 0; } ... I actually wrote that snippet awhile back but I'm rusty with C++ these days and will have to see if I can get it working again. Would love if there was a built-in or user-contributed study that did a Ctrl-Insert reload+recalc automagically on Bar-Close so the CPU load was low. |
| [2025-04-02 14:53:21] |
| User35525 - Posts: 184 |
|
Got my custom function to compile again. Just a wish - it could be great if I could set sc.ChartUpdateIntervalInMilliseconds. I'd set to '200' if my custom BarCloseRecalc function was enabled and to '500' or '1000' otherwise. |
To post a message in this thread, you need to log in with your Sierra Chart account: