Support Board
Date/Time: Wed, 30 Apr 2025 10:44:51 +0000
PLATFORM FREEZING UP
View Count: 455
| [2023-01-26 14:59:57] |
| User410836 - Posts: 18 |
|
Hi, For last couple of days my Sierra platform and charts freeze off and on frequently. Kindly advise. |
| [2023-01-26 15:03:52] |
| Sierra_Chart Engineering - Posts: 19383 |
|
Refer to this page: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often 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 |
| [2025-04-11 04:16:55] |
| Meklon - Posts: 229 |
|
I am familiar with this page you have referred me to. However, I have once again thoroughly went over every topic and can assure you that machine resources are NOT an issue here - I have plenty of RAM and CPU available. This is a very powerful custom server specifically designed and built for trading purpose by Trading Computers (they do know what they are doing). I have been using this machine for an extended period and never had this issue before. The fact that this event of freezing is happening 2 times every day at the EXACT time (6 PM EST and 12 AM EST) is clearly demonstrating that at the specified times platform is initiating some sort of activity that is related to rebuilding of all charts in the chart books. Perhaps similar to disconnect and reconnect to a data feed. Even currently, in the period of unprecedented volatility of the past 2 weeks same exact platform with same exact set of chartbook is operating flawlessly during the regular trading hours and during the night while the market speed and volume are 10 times (if not more) exceeds normal trading conditions. Not a single hiccup. Hence, this is not a hardware resource issue. Nevertheless, this freezing event is happening only on the platform connected to a live account (ONLY live account, a copy of Sierra installation on the same server connected to Sierra Sym is not experiencing this problem). Freezing of a live trading platform is taking place EXACTLY at 6 PM EST and 12 AM EST. This is NOT a random event, and the problem is NOT intermittent. Is there a platform setting that can be deactivated in order to prevent the automatic connect / disconnect to the data feed that is forcing to rebuild all chartbooks at the specified times? Please advise. Date Time Of Last Edit: 2025-04-11 04:25:51
|
| [2025-04-11 11:43:44] |
| Sierra_Chart Engineering - Posts: 19383 |
|
Is there a platform setting that can be deactivated in order to prevent the automatic connect / disconnect to the data feed that is forcing to rebuild all chartbooks at the specified times?
Is there a reconnection that is actually occurring at the time the problem is occurring? 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-11 11:45:16
|
| [2025-04-11 13:27:15] |
| Meklon - Posts: 229 |
|
I cannot say for certain if the actual reconnect is occurring, but platform entirely freezes at exactly 6 PM EST and 12 AM EST every day as well as at the Sunday 6 PM EST open. It appears that for whatever reason at the specified times platform initiates a request to recalculate all charts. This has not happened before and started happening about 10 days ago. Here is the excerpt from the log at 12 AM EST from this past night 9 hours ago: 2025-04-10 23:14:22.954 | Saved Chartbook: Trend-Detector-EXECUTION.Cht. Time: 0.5332 seconds. 2025-04-10 23:44:29.302 | Saved Chartbook: ES - MINI - Bare_Minimum.cht. Time: 0.9070 seconds. 2025-04-10 23:44:29.709 | Saved Chartbook: NQ - MINI - Bare_Minimum.Cht. Time: 0.4053 seconds. 2025-04-10 23:44:29.954 | Saved Chartbook: Trend-Detector-CONTEXT.Cht. Time: 0.2445 seconds. 2025-04-10 23:44:30.506 | Saved Chartbook: Trend-Detector-EXECUTION.Cht. Time: 0.5495 seconds. 2025-04-11 00:00:05.409 | Added historical Daily data request for ESM25_FUT_CME to the queue. 2025-04-11 00:00:05.409 | Triggering next historical data download in queue. 2025-04-11 00:00:05.415 | HD Request # 85 | Downloading Historical Daily chart data for ESM25_FUT_CME. Starting date: 2025-04-09. Service: sc_futures_direct.dtc.trading 2025-04-11 00:00:05.416 | Added historical Daily data request for NQM25_FUT_CME to the queue. 2025-04-11 00:00:05.416 | Triggering next historical data download in queue. 2025-04-11 00:00:05.737 | HD Request # 85 | Requesting historical Daily data for ESM25 starting at 2025-04-08. SC External HD service. 2025-04-11 00:00:05.876 | HD Request # 85 | Receiving historical Daily data for ESM25_FUT_CME starting at 2025-04-09. 2025-04-11 00:00:05.877 | HD Request # 85 | Writing historical Daily data to the file ESM25_FUT_CME.dly. 2025-04-11 00:00:05.882 | HD Request # 85 | Bytes received: 236 2025-04-11 00:00:05.882 | HD Request # 85 | Received 4 Daily data records from 2025-04-09 00:00:00 to 2025-04-11 00:00:00 (3.0 days) and wrote 3 records for ESM25_FUT_CME 2025-04-11 00:00:05.883 | HD Request # 85 | Completion time: 0s. 2025-04-11 00:00:05.883 | HD Request # 85 | Daily data download complete for ESM25_FUT_CME. Unique request ID: 109 2025-04-11 00:00:05.883 | Removing historical data download ID 109. 2025-04-11 00:00:05.884 | 2025-04-11 00:00:05.884 | Triggering next historical data download in queue. 2025-04-11 00:00:05.886 | HD Request # 86 | Downloading Historical Daily chart data for NQM25_FUT_CME. Starting date: 2025-04-09. Service: sc_futures_direct.dtc.trading 2025-04-11 00:00:06.105 | HD Request # 86 | Requesting historical Daily data for NQM25 starting at 2025-04-08. SC External HD service. 2025-04-11 00:00:06.208 | HD Request # 86 | Receiving historical Daily data for NQM25_FUT_CME starting at 2025-04-09. 2025-04-11 00:00:06.208 | HD Request # 86 | Writing historical Daily data to the file NQM25_FUT_CME.dly. 2025-04-11 00:00:06.213 | HD Request # 86 | Bytes received: 245 2025-04-11 00:00:06.213 | HD Request # 86 | Received 4 Daily data records from 2025-04-09 00:00:00 to 2025-04-11 00:00:00 (3.0 days) and wrote 3 records for NQM25_FUT_CME 2025-04-11 00:00:06.213 | HD Request # 86 | Completion time: 1s. 2025-04-11 00:00:06.213 | HD Request # 86 | Daily data download complete for NQM25_FUT_CME. Unique request ID: 110 2025-04-11 00:00:06.213 | Removing historical data download ID 110. 2025-04-11 00:00:06.214 | 2025-04-11 00:00:06.214 | No download requests in the queue to start downloads for. 2025-04-11 00:00:07.401 | ESM25_FUT_CME[M] Daily #27 | Reloading chart. 2025-04-11 00:00:07.425 | NQM25_FUT_CME [CB][M] Daily #30 | Reloading chart. 2025-04-11 00:00:07.869 | Chart #27 has tagged chart #13 for full recalculation. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:00:07.869 | Chart #27 has tagged chart #36 for full recalculation. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:00:07.869 | Chart #27 has tagged chart #37 for full recalculation. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:00:07.870 | ESM25_FUT_CME[M] Daily #27 | Chart data loading complete. 2025-04-11 00:00:08.044 | NQM25_FUT_CME [CB][M] Daily #30 | Chart data loading complete. 2025-04-11 00:00:13.047 | ESM25_FUT_CME [CB][M] 5000 Trades #37 | Performing a full recalculation because it has been tagged. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:00:16.786 | ESM25_FUT_CME [CB][M] 5000 Trades #37 | Study: -ET Price Rejector Pro | Making HTTP request. 2025-04-11 00:07:49.914 | ESM25_FUT_CME [CB][M] 5000 Trades #36 | Performing a full recalculation because it has been tagged. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:07:50.063 | ESM25_FUT_CME [CB][M] 5000 Trades #36 | Study: -ET Price Rejector Pro | Making HTTP request. 2025-04-11 00:15:18.152 | Chart #36 has tagged chart #16 for full recalculation. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:15:24.289 | ESM25_FUT_CME [CB][M] Daily #2 | Reloading chart. 2025-04-11 00:15:24.790 | NQM25_FUT_CME [CB][M] Daily #4 | Reloading chart. 2025-04-11 00:15:25.251 | ESM25_FUT_CME [CB][M] Daily #2 | Chart data loading complete. 2025-04-11 00:15:25.254 | NQM25_FUT_CME[M] Daily #27 | Reloading chart. 2025-04-11 00:15:25.272 | NQM25_FUT_CME [CB][M] Daily #30 | Reloading chart. 2025-04-11 00:15:25.698 | Chart #27 has tagged chart #18 for full recalculation. Chartbook: NQ - MINI - Bare_Minimum.Cht 2025-04-11 00:15:25.698 | NQM25_FUT_CME[M] Daily #27 | Chart data loading complete. 2025-04-11 00:15:25.712 | NQM25_FUT_CME [CB][M] Daily #4 | Chart data loading complete. 2025-04-11 00:15:25.715 | ESM25_FUT_CME [CB][M] Daily #29 | Reloading chart. 2025-04-11 00:15:26.185 | Chart #30 has tagged chart #15 for full recalculation. Chartbook: Trend-Detector-CONTEXT.Cht 2025-04-11 00:15:26.185 | NQM25_FUT_CME [CB][M] Daily #30 | Chart data loading complete. 2025-04-11 00:15:26.188 | ESM25_FUT_CME [CB][M] Daily #29 | Reloading chart. 2025-04-11 00:15:26.734 | Chart #29 has tagged chart #13 for full recalculation. Chartbook: Trend-Detector-CONTEXT.Cht 2025-04-11 00:15:26.734 | ESM25_FUT_CME [CB][M] Daily #29 | Chart data loading complete. | Number times message added: 1 2025-04-11 00:15:27.333 | ESM25_FUT_CME [CB][M] #13 | Performing a full recalculation because it has been tagged. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:15:27.758 | ESM25_FUT_CME [CB][M] 610 Trades #16 | Performing a full recalculation because it has been tagged. Chartbook: ES - MINI - Bare_Minimum.cht 2025-04-11 00:15:29.649 | ESM25_FUT_CME [CB][M] 610 Trades #16 | Study: -ET Price Rejector Pro | Making HTTP request. 2025-04-11 00:42:46.764 | NQM25_FUT_CME [CB][M] #18 | Performing a full recalculation because it has been tagged. Chartbook: NQ - MINI - Bare_Minimum.Cht 2025-04-11 00:42:48.112 | ESM25_FUT_CME [CB][M] #13 | Performing a full recalculation because it has been tagged. Chartbook: Trend-Detector-CONTEXT.Cht 2025-04-11 00:42:51.073 | NQM25_FUT_CME [CB][M] #15 | Performing a full recalculation because it has been tagged. Chartbook: Trend-Detector-CONTEXT.Cht 2025-04-11 00:42:58.092 | Saved Chartbook: ES - MINI - Bare_Minimum.cht. Time: 1.2408 seconds. 2025-04-11 00:42:58.533 | Saved Chartbook: NQ - MINI - Bare_Minimum.Cht. Time: 0.4395 seconds. 2025-04-11 00:42:58.790 | Saved Chartbook: Trend-Detector-CONTEXT.Cht. Time: 0.2547 seconds. 2025-04-11 00:42:59.349 | Saved Chartbook: Trend-Detector-EXECUTION.Cht. Time: 0.5582 seconds. 2025-04-11 01:13:05.908 | Saved Chartbook: ES - MINI - Bare_Minimum.cht. Time: 0.9901 seconds. 2025-04-11 01:13:06.378 | Saved Chartbook: NQ - MINI - Bare_Minimum.Cht. Time: 0.4677 seconds. 2025-04-11 01:13:06.645 | Saved Chartbook: Trend-Detector-CONTEXT.Cht. Time: 0.2663 seconds. 2025-04-11 01:13:07.269 | Saved Chartbook: Trend-Detector-EXECUTION.Cht. Time: 0.6219 seconds. 2025-04-11 01:25:47.674 | Saved Chartbook: ES - MINI - Bare_Minimum.cht. Time: 1.0744 seconds. 2025-04-11 01:25:48.060 | Saved Chartbook: NQ - MINI - Bare_Minimum.Cht. Time: 0.3851 seconds. |
| [2025-04-11 16:20:48] |
| Sierra_Chart Engineering - Posts: 19383 |
|
Check the times that you have set Sierra Chart to download Historical Daily Data: Downloading Historical Daily Data The problem is, there is some significant inefficiency you have in one or more charts causing the problem. You will need to close each chart one by one until you determine which one has the problem. The other thing to do is to move the complex charts to a sub instance so they do not cause any problem: Using DTC Server for Data and Trading in Another Sierra Chart Instance 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-11 16:22:11
|
| [2025-04-11 17:38:09] |
| Meklon - Posts: 229 |
|
What you are saying makes sense. I was already considering moving the TPO and long-term / high timeframe historical charts to another instance to segregate the execution instance and algo-activity from the heavy recalculation load. Thank you for your pointers and confirming what I've suspected. I will investigate further to identify and isolate the culprit. Date Time Of Last Edit: 2025-04-11 18:00:27
|
To post a message in this thread, you need to log in with your Sierra Chart account: