Support Board
Date/Time: Thu, 07 May 2026 18:18:37 +0000
Number bar chart lagging occasionally
View Count: 25
| [2026-05-07 15:17:04] |
| User763335 - Posts: 128 |
|
Hi am noticing on occasions, the number bars are not printing in real-time and lag the clock by few seconds (and even other trading platforms like DasTrader). What I mean is this, - say the current time is 10:01:03, meaning the first minute is complete(past 10am) and we're 3 seconds into the second minute - the number bar chart is still finishing up the 1st minute bar, while the clock is into 2nd minute and Dastrader already started printing the 2nd minute bar. - few seconds(usually 2-3 seconds) later, the Number bar charts starts printing the 2nd minute bar.I just lost visibility into the tape for these few seconds. As a scalper, reading the tape for my entries, these few seconds matter to me. Noticing the issue during higher trading activity/volume after market open(the latest was between 09:50am-10:10am NYT). The CPU/memory/GPU usage is pretty light on the system( usually 30-40% peaks). The hard drive for the whole system is on internal SSD. The concerned ticker is $NVDA_MBO. Have attached a copy of the Chart Settings->Performance from the concerned Footprint chart. Global Settings->Data/Trade Service Settings->Intraday Data Storage Time Unit=1 Tick Number bars Study: Require 1 Tick Intraday Data Storage Time Unit=Yes Symbol Settings: Tick Size=0.01 Display: Chart Update Interval:Chart Update Interval in Milliseconds=50 Graphics Settings Global: Use OpenGL for Chart Graphics, Checked. SC version 2899 pls advise, Thanks Date Time Of Last Edit: 2026-05-07 15:29:51
|
Private File |
| [2026-05-07 17:22:48] |
| John - SC Support - Posts: 46003 |
|
You can not look at only the clock for your computer and determine this. You need to understand how different your clock is from the exchange clock. The exchange uses the national standard clock. If you open your Message Log, and start looking from the top down, you will find entries that state the following: 2026-05-07 11:04:41.592 | 2026-05-07 16:04:41 Local computer time in UTC
2026-05-07 11:04:41.592 | 2026-05-07 11:04:41 Local computer time in SC Time Zone 2026-05-07 11:04:41.592 | 2026-05-07 16:04:37 Server time in UTC 2026-05-07 11:04:41.592 | Local computer UTC time and Server UTC time difference: 4 seconds. In this case (my computer) my computer clock is different from the exchange uses by 4 seconds. So if my computer clock says that it is 10:01:03, then a new bar should NOT be started yet, as the exchange data is at 10:00:59. Then, you need to look at the "Data Delay" entry in the Chart Header to see how much delay you are getting IN ADDITION TO the difference in your computer clock and the exchange. In the chart header, this Data Delay entry will be prefixed with "DD:", and gives you the instantaneous difference between your computer clock at the exchange clock. Again, you need to take into account the difference without any data flowing, which is what you got from the above. If you do not have the Data Delay showing in the Chart Header, then refer to the following to add it, or move it to where you can view it: Working With Charts: Region Data Line / Chart Header Once you understand what is occurring with the data, then you can go through the items at the following link for how improve performance: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: