Support Board
Date/Time: Wed, 30 Apr 2025 04:25:04 +0000
Extended Load Time for Charts
View Count: 86
| [2025-04-28 16:08:21] |
| Oz - Posts: 53 |
|
Hi I’ve been using Sierra for a couple of years now with the same charts, studies and screen layouts. Recently the load time for my charts has increased dramatically with the delay appearing to be: Waiting to Download Historical Data This is where the stall begins and load takes anywhere from 5-10 minutes a times. I’ve read your High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often and made some changes but continue to have extended times in loading charts even though I have not made drastic changes to my charts for some time. I’ve cleared some of the data files not being used and reloaded data. I then started in safe mode. Still continued to get delayed and extended loading times even when in safe mode. I’ve checked the message log and there seems to be some delay between the cycles of opening sockets and closing of these and then attempts to connect again with these cycles happening in spurts. I’ve noticed this over the last couple of weeks but it’s getting to stage where it’s not workable now. I’ve attached a couple of screenshots of parts of the message log. In this instance there was a nearly a 5 minute stall between connections (sscreenshot2). I’ve never had these issues before until recent upgrade to the current version. Once the charts update the software runs fine, it’s just the loading and uploading of data at start up. Any assistance is greatly appreciated. Thank you. |
Attachment Deleted. Private File Private File |
| [2025-04-28 17:29:08] |
| John - SC Support - Posts: 39559 |
|
This is most likely due to the high trading volumes that are occurring lately, so there is more data to download when you get connected. Refer to the following regarding this: Improving Performance with Wider Price Ranges and Increased Trading Activity For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-04-29 16:18:37] |
| Barry L - Posts: 35 |
|
John , Oz is in a Discord with me and he DMd me last week about these lag issues. I'm also in a another room with two experienced users who are also seeing all the same problems, It started a few weeks ago when I had to update from Ver 2644 to 2742 or above to run a DLL that a friend did for me, Ever since them its been a nightmare, I tried everything you suggested in that post, cut a lot of chartbook bloat made the days to upload as short as possible went to 3000 ms on charts that didn't need to be fast. even did that Windows graphics change ( Best performance) tried all the various setting in OS timers on /off etc it helped a little, but I still see up to a 4 sec delay in the T & S time stamps when I compare it to IB TWS I have running off to the side, was on 2748 the last 2 days and it been the worst ever , today I went back to 2644 again just to see and there very little lag , but I cant run the 2 DLLs and also all my right click chart drop down menu I customized is blank now, The time before when I went back to 2644 it went back to the default, Whatever got changed around the 2700 mark concerning Timers has made it worse , Its not just a data lag problem, the whole platform is far stickier, even when the market is dead quiet, You get delays in moving around menus and as I have all my charts on sync scroll linked , when u roll the mousewheel , its very laggy and sticky , it works perfect on ver 2644 with the same Chartbook Any other suggestions other than just not trade high volume times ? . Its not my computer , it was all upgraded 2 months ago and is plenty fast Barry |
| [2025-04-29 17:17:58] |
| Sierra_Chart Engineering - Posts: 19383 |
|
There definitively is not lower performance with newer versions. The very opposite, higher performance in some cases. Refer to: 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 Although using Sierra Chart timers and operating system timers does make an apparent difference with performance: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often: 30.58 - Using Sierra Chart Timers for Faster Updates To improve performance: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often: 30.48 - Basic Steps to Resolve Performance Issue in Sierra Chart This is because you are in Thailand, and using a full tick by tick feed: but I still see up to a 4 sec delay in the T & S time stamps when I compare it to IB TWS
Interactive Brokers data is snapshot. We do not accept this: , today I went back to 2644 again just to see and there very little lag , There could not be a difference, with data feed lag between versions. This is just simply not possible. There is some other explanation in your case. If the entire Sierra Chart program is being affected and there is more processing occurring, then this would be an explanation.You get delays in moving around menus and as I have all my charts on sync scroll linked , when u roll the mousewheel , its very laggy and sticky , it works perfect on ver 2644 with the same Chartbook Do not use Sierra Chart timers. Use operating system timers.
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: 2025-04-29 17:21:37
|
| [2025-04-29 17:34:08] |
| Barry L - Posts: 35 |
|
I wrote this but I didn't see the 2nd bit of your reply after snap shot , did u edit it ? The one thing I didn't try as I didn't see it before , was changing from 1 Tick to 1 Second or more, this seems to have helped a little, But if I disconnect then reconnect or delete and download data it seem to revert back to the 1 tick default, Also my B 10 custom symbol of biggest weights in SPY isn't working. is this because its stored in 1 tick data and it cant read it in 1 sec ? How can I get it to lock on 1 sec then delete all the 1 tick data and reload it in 1 sec format ? Why would the mouse wheel scroll and menus be so sticky in ver 2755 compared to 2644 even when both are disconnected from he data feed and why do I not get the lag compared to IB when I run 2644 ? , I'm still the same distance away, 1 of the userS who are getting the same lag is in Michigan far closer to CME . I am on OS timers Barry Date Time Of Last Edit: 2025-04-29 17:48:45
|
| [2025-04-29 17:38:07] |
| Oz - Posts: 53 |
|
Barry, Thank you for your reply. The issues started for me probably about a month ago too. I've been trying all sorts of different things too. I've started running 2 instances of Sierra and culled most of my charts to a minimum. I'm running a higher time-frame instance and a lower time-frame instance. Higher time-frame charts take some time to load but once running are passable for now, maybe a little sticky. The shorter time-frame charts seem ok these only load 1-3 days of tick data. I'm getting by with this for now, but certainly hope there is improvement with the new Sierra Upgrades being done currently. I also see some latency from time to time especially when the markets go into crazy mode. I execute on another platform and there is minimal latency there, but i understand what you are saying. If you are getting minimal latency with IB you may need to execute directly on their platform when the market is in wild mode. Just an idea. |
| [2025-04-30 01:22:01] |
| Oz - Posts: 53 |
|
I've had a closer look at my logs and as mentioned previously the load times and download times have been extended over the last few weeks. I see many logs when starting Sierra with the following: Windows error code 10061: No connection could be made because the target machine actively refused it. When comparing logs from earlier this year I never had this during loading and start up. Could this be an issue, can this be rectified at my end or is this happening due to your end? Thank you. |
To post a message in this thread, you need to log in with your Sierra Chart account: