Support Board
Date/Time: Mon, 25 Nov 2024 22:53:00 +0000
High RAM memory usage
View Count: 537
| [2024-01-31 17:12:42] |
| User308424 - Posts: 70 |
|
Hi there, I was facing issues as one of SC instance consume around 4,4GB of RAM memory. That was possibly causing issues with new data to be loaded. My trades are executed with a delay. I am having just 1 chart loaded on one instance. Another instance is just for connection purposes. I limited number of historical days to load to 10, for intraday chart I load only 3 days. Intraday Data Storage Time Unit I keep to 1 tick. I turned off some of my studies leaving just a couple of them and managed to get down to about 1,5GB of usage which is still a lot. I followed this manual from point 30 that I found on Support Board. https://www.sierrachart.com/index.php?l=doc/helpdetails30.html#TooMuchDataToLoadOrLoaded My PC is quite new with above average spec but I have a feeling I need to optimize SC a bit. Is there anything else I could potentially do to limit RAM usage further down? What would be an average RAM consumption? Thanks in advance! |
| [2024-01-31 18:27:16] |
| John - SC Support - Posts: 36286 |
|
Everything we can suggest is in Help Topic 30 which you have already reviewed. Your memory usage is going to depend on how much data and what studies are loaded. It sounds like you have done everything you should have done.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-01-31 19:53:52] |
| User308424 - Posts: 70 |
|
Hey John, thanks for support on this. Following manuals I found here: Prices / Data Falling Behind: 4.1 - Different Servers I noticed that I receive Delayed Data - despite the fact that it supposed to be a live data coming in from Rithmic. When I add Delay Data in chart hearder I see that value keep on increasing (see attached picture). When I disconnect and reconnect that value seems to fall down to 0 and then again it keeps on increasing. Do you think realigning of the PC/SC time would help? Any suggestions?? Thanks in advance! |
| Attachment Deleted. |
DD.jpg| [2024-01-31 22:53:45] |
| John - SC Support - Posts: 36286 |
|
Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Close all of the Chartbooks with "File >> Close All Chartbooks". Open a single chart for the symbol you have an issue with through "File >> Find Symbol". Tell us that symbol of the chart. Tell us about *one* symbol only. Disconnect from the data feed with "File >> Disconnect". Connect to the data feed with "File >> Connect to Data Feed". After the connection and after about 10 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-01 14:37:08] |
| User308424 - Posts: 70 |
|
Hi John, log below. I selected ESH4.CME symbol. What I noticed also is that during the night and before the opening DataDelay was max of 2-3 seconds. When market was opened DataDelay increased again to about 40 seconds. Thanks for any assistance with the topic. LOG 2024-02-01 08:32:16.562 | Software version: 2586 64-bit 2024-02-01 08:32:16.563 | OpenGL enabled (NVIDIA Corporation/NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2) 2024-02-01 08:32:16.563 | Primary Thread ID: 9100 2024-02-01 08:32:16.563 | Usage end date: 2024-02-26 2024-02-01 08:32:16.563 | Enabled for: Advanced Features 2. 2024-02-01 08:32:16.563 | Enabled for: Sierra Chart Historical Data Service. 2024-02-01 08:32:16.563 | Enabled for: Denali Real-Time Exchange Data Feed. 2024-02-01 08:32:16.563 | Enabled for: Delayed Denali Exchange Data Feed. 2024-02-01 08:32:16.563 | Allow Support for Sierra Chart Data Feeds is enabled. 2024-02-01 08:32:16.563 | Current selected Data/Trading service: Rithmic Direct - DTC 2024-02-01 08:32:16.563 | Custom symbol settings values: enabled 2024-02-01 08:32:16.563 | Chart Update Interval: 200 2024-02-01 08:32:16.563 | Intraday Data Storage Time Unit: 0 2024-02-01 08:32:16.563 | Time Zone: -06:00:00 (CST-06CDT+01,M3.2.0/02:00,M11.1.0/02:00) 2024-02-01 08:32:16.563 | 2024-02-01 14:32:16 Local computer time in UTC 2024-02-01 08:32:16.563 | 2024-02-01 08:32:16 Local computer time in SC Time Zone 2024-02-01 08:32:16.563 | 2024-02-01 06:24:49 Server time in UTC 2024-02-01 08:32:16.563 | Local computer UTC time and Server UTC time difference: 0 seconds. 2024-02-01 08:32:16.563 | Program path: D:\SierraChart\SC1\ 2024-02-01 08:32:16.563 | Data Files path: D:\SierraChart\SC1\Data\ 2024-02-01 08:32:16.563 | OS Version Number: 10.0 2024-02-01 08:32:16.563 | Locale Setting: C 2024-02-01 08:32:16.563 | DLLs: sst_FreeBundle_2273_64.dll, sst_FreeBundle_64.dll, UserContributedStudies_64.dll 2024-02-01 08:32:16.563 | Allowed protected custom studies: SST_FreeBundle, zyp_download_free 2024-02-01 08:32:16.563 | Crash reporter started: true 2024-02-01 08:32:16.563 | 2024-02-01 08:32:44.463 | ESH4.CME 1 Min #1 | Reloading chart. 2024-02-01 08:33:09.446 | File >> Disconnect selected. 2024-02-01 08:33:09.446 | Rithmic Direct - DTC (Data) | Waiting for socket receive thread to end 2024-02-01 08:33:09.447 | DTC Client socket (4) | CloseSocket call. 2024-02-01 08:33:09.447 | DTC Client socket (4) | Shutdown started. Waiting for graceful close. 2024-02-01 08:33:09.447 | Rithmic Direct - DTC (Data) | Disconnected from the server. 2024-02-01 08:33:09.448 | Rithmic Direct - DTC | Waiting for socket receive thread to end 2024-02-01 08:33:09.448 | DTC Client socket (1) | CloseSocket call. 2024-02-01 08:33:09.448 | DTC Client socket (1) | Max send buffers used during socket life: 3 2024-02-01 08:33:09.448 | DTC Client socket (1) | Max send buffer size during socket life: 970 2024-02-01 08:33:09.448 | DTC Client socket (1) | Shutdown started. Waiting for graceful close. 2024-02-01 08:33:09.448 | Rithmic Direct - DTC | Disconnected. 2024-02-01 08:33:09.660 | DTC Client socket (1) | Socket gracefully closed by remote side. 2024-02-01 08:33:09.660 | DTC Client socket (1) | Closed. 2024-02-01 08:33:20.434 | 2024-02-01 08:33:20.434 | Rithmic Direct - DTC | Using server connection: Apex-Chicago Area-Non-Aggregated 2024-02-01 08:33:20.434 | Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50528 2024-02-01 08:33:20.635 | DTC Client socket (1) | Creating socket. Using TLS 1.2. 2024-02-01 08:33:20.635 | DTC Client socket (1) | New receive buffer size: 0 2024-02-01 08:33:20.635 | DTC Client socket (1) | Connecting to IP: 216.57.156.163. 2024-02-01 08:33:20.920 | Rithmic Direct - DTC | Network connection to server complete. 2024-02-01 08:33:20.920 | Rithmic Direct - DTC | Starting socket receive thread. 2024-02-01 08:33:20.920 | Rithmic Direct - DTC | Setting DTC encoding to Binary 2024-02-01 08:33:20.920 | Rithmic Direct - DTC | Sending logon request message. 2024-02-01 08:33:20.958 | DTC Client socket (4) | Socket gracefully closed by remote side. 2024-02-01 08:33:20.959 | DTC Client socket (4) | Closed. 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Received logon response. 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Server Name: . 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Successfully connected. 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Trading is supported. 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Order cancel and replace is supported. 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | OCO Orders supported. 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Symbol and Exchange Delimiter: . 2024-02-01 08:33:21.473 | Rithmic Direct - DTC | Connected to server complete. 2024-02-01 08:33:21.474 | No download requests in the queue to start downloads for. 2024-02-01 08:33:21.474 | No download requests in the queue to start downloads for. 2024-02-01 08:33:21.474 | No download requests in the queue to start downloads for. 2024-02-01 08:33:21.474 | No download requests in the queue to start downloads for. 2024-02-01 08:33:21.474 | Notice: Not connected to Live trading account to receive CME realtime futures data at non-professional fees. 2024-02-01 08:33:21.481 | HD Server Manager | Incoming connection from IP: 127.0.0.1 2024-02-01 08:33:21.481 | HD Server Manager | Started new historical data server. Count=1 2024-02-01 08:33:21.486 | HD Server | Thread:21292 (3) | Creating socket. 2024-02-01 08:33:21.486 | HD Server | Thread:21292 (3) | New receive buffer size: 262144 2024-02-01 08:33:21.487 | HD Server | Thread:21292 (3) | Allocated send buffers: 32 of 4096 bytes. 2024-02-01 08:33:21.487 | HD Server | Setting DTC encoding to Binary VLS | Thread:21292 2024-02-01 08:33:21.487 | HD Server | Received login. Requesting authorization. | Username: AC120616. | Thread:21292 2024-02-01 08:33:21.487 | HD Server | Login has been authorized. | Username: AC120616. | Thread:21292 2024-02-01 08:33:21.487 | HD Server | HD Request #7 | Socket: 3 | Symbol: ESH4.CME | ServiceCode: DTCSubInstance | RecordInterval: 0 | MaximumDaysRequested: 0 | Start date-time: 2024-02-01 14:31:41 | ClientReqID: 7 | Username: AC120616. | Thread:21292 2024-02-01 08:33:21.487 | Rithmic Direct - DTC | Using primary service for historical data for ESH4.CME 2024-02-01 08:33:21.487 | Historical data service client indicated that downloads are not enabled. Symbol: ESH4.CME. Data Type: Intraday data. 2024-02-01 08:33:21.487 | Historical data download ID 10 not found when removing ID from outstanding request set. 2024-02-01 08:33:21.488 | Using symbol data fast lookup vector 2024-02-01 08:33:21.488 | Rithmic Direct - DTC | Starting real-time market data updates for: ESH4.CME. ID: 1 Service code: rithmic.trading 2024-02-01 08:33:21.489 | Rithmic Direct - DTC (Data) | Connecting to the server rsc.rithmic.com. Port 50529 2024-02-01 08:33:21.490 | DTC Client socket (4) | Creating socket. Using TLS 1.2. 2024-02-01 08:33:21.490 | DTC Client socket (4) | New receive buffer size: 0 2024-02-01 08:33:21.490 | DTC Client socket (4) | Connecting to IP: 216.57.156.163. 2024-02-01 08:33:21.491 | Rithmic Direct - DTC | Requesting security definition data for: ESH4.CME. ID: 1 2024-02-01 08:33:21.491 | Real-time Intraday chart data file updates started for ESH4.CME 2024-02-01 08:33:21.491 | Intraday chart data file opened for ESH4.CME 2024-02-01 08:33:21.710 | Rithmic Direct - DTC | Starting real-time market data updates for: MESH4.CME. ID: 2 Service code: rithmic.trading 2024-02-01 08:33:21.710 | Rithmic Direct - DTC | Requesting security definition data for: MESH4.CME. ID: 2 2024-02-01 08:33:21.710 | Requesting market depth updates for: ESH4.CME if supported. NumLevels=1400 2024-02-01 08:33:21.710 | Separate subscription for market depth updates not supported. ESH4.CME 2024-02-01 08:33:21.710 | Requesting market depth updates for: MESH4.CME if supported. NumLevels=1400 2024-02-01 08:33:21.710 | Separate subscription for market depth updates not supported. MESH4.CME 2024-02-01 08:33:21.737 | Rithmic Direct - DTC (Data) | Network connection to server complete. 2024-02-01 08:33:21.737 | Rithmic Direct - DTC (Data) | Starting socket receive thread. 2024-02-01 08:33:21.737 | Rithmic Direct - DTC (Data) | Setting DTC encoding to Binary 2024-02-01 08:33:21.737 | Rithmic Direct - DTC (Data) | Sending logon request message. 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Received logon response. 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Server Name: . 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Server protocol version: 8. Client protocol version: 8 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Successfully connected. 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Trading is not supported. 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Symbol and Exchange Delimiter: . 2024-02-01 08:33:22.414 | Rithmic Direct - DTC | Using primary service for historical data for ESH4.CME 2024-02-01 08:33:22.414 | Historical data service client indicated that downloads are not enabled. Symbol: ESH4.CME. Data Type: Intraday data. 2024-02-01 08:33:22.414 | Historical data download ID 11 not found when removing ID from outstanding request set. 2024-02-01 08:33:22.414 | Real-time Intraday chart data file updates started for ESH4.CME 2024-02-01 08:33:22.414 | Intraday chart data file opened for ESH4.CME 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Restarting real-time data updates for symbol: ESH4.CME. Market Depth data restarted. 2024-02-01 08:33:22.414 | Rithmic Direct - DTC (Data) | Restarting real-time data updates for symbol: MESH4.CME. Market Depth data restarted. 2024-02-01 08:33:22.475 | HD Server | HD Request | Socket: 3 | Symbol: ESH4.CME | ServiceCode: DTCSubInstance | RecordInterval: 0 | Records Served: 3 | ClientReqID: 7 | Username: AC120616. | Thread:21292 2024-02-01 08:33:22.476 | HD Server | Thread:21292 (3) | Socket gracefully closed by remote side. 2024-02-01 08:33:22.476 | HD Server | Thread:21292 (3) | CloseSocket call. 2024-02-01 08:33:22.476 | HD Server | Thread:21292 (0) | CloseSocket call. 2024-02-01 08:33:22.476 | HD Server | Thread:21292 (3) | Graceful close received or receive error. Shutdown complete. Closing socket now. 2024-02-01 08:33:22.476 | HD Server | Thread:21292 (3) | Closed. 2024-02-01 08:33:22.477 | HD Server | Thread:21292 (0) | CloseSocket call. 2024-02-01 08:33:22.478 | HD Server Manager | Incoming connection from IP: 127.0.0.1 2024-02-01 08:33:22.478 | HD Server Manager | Started new historical data server. Count=2 2024-02-01 08:33:22.483 | HD Server | Thread:13016 (3) | Creating socket. 2024-02-01 08:33:22.483 | HD Server | Thread:13016 (3) | New receive buffer size: 262144 2024-02-01 08:33:22.483 | HD Server | Thread:13016 (3) | Allocated send buffers: 32 of 4096 bytes. 2024-02-01 08:33:22.483 | HD Server | Setting DTC encoding to Binary VLS | Thread:13016 2024-02-01 08:33:22.484 | HD Server | Received login. Requesting authorization. | Username: AC120616. | Thread:13016 2024-02-01 08:33:22.484 | HD Server | Login has been authorized. | Username: AC120616. | Thread:13016 2024-02-01 08:33:22.484 | HD Server | HD Request #8 | Socket: 3 | Symbol: MESH4.CME | ServiceCode: DTCSubInstance | RecordInterval: 0 | MaximumDaysRequested: 0 | Start date-time: 2024-02-01 14:31:40 | ClientReqID: 8 | Username: AC120616. | Thread:13016 2024-02-01 08:33:22.484 | Rithmic Direct - DTC | Using primary service for historical data for MESH4.CME 2024-02-01 08:33:22.484 | Historical data service client indicated that downloads are not enabled. Symbol: MESH4.CME. Data Type: Intraday data. 2024-02-01 08:33:22.484 | Historical data download ID 12 not found when removing ID from outstanding request set. 2024-02-01 08:33:22.484 | Real-time Intraday chart data file updates started for MESH4.CME 2024-02-01 08:33:22.484 | Intraday chart data file opened for MESH4.CME 2024-02-01 08:33:22.522 | HD Server | Server thread ending. Closing socket. | Username: AC120616. | Thread:21292 2024-02-01 08:33:22.522 | HD Server Manager | Current server count=1 2024-02-01 08:33:22.673 | Rithmic Direct - DTC (Data) | Clearing market depth for ESH4.CME 2024-02-01 08:33:23.485 | HD Server | HD Request | Socket: 3 | Symbol: MESH4.CME | ServiceCode: DTCSubInstance | RecordInterval: 0 | Records Served: 22 | ClientReqID: 8 | Username: AC120616. | Thread:13016 2024-02-01 08:33:23.485 | HD Server | Thread:13016 (3) | Socket gracefully closed by remote side. 2024-02-01 08:33:23.485 | HD Server | Thread:13016 (3) | CloseSocket call. 2024-02-01 08:33:23.486 | HD Server | Thread:13016 (0) | CloseSocket call. 2024-02-01 08:33:23.486 | HD Server | Thread:13016 (3) | Graceful close received or receive error. Shutdown complete. Closing socket now. 2024-02-01 08:33:23.486 | HD Server | Thread:13016 (3) | Closed. 2024-02-01 08:33:23.486 | HD Server | Thread:13016 (0) | CloseSocket call. 2024-02-01 08:33:23.522 | HD Server | Server thread ending. Closing socket. | Username: AC120616. | Thread:13016 2024-02-01 08:33:23.522 | HD Server Manager | Current server count=0 2024-02-01 08:33:24.259 | Rithmic Direct - DTC (Data) | Clearing market depth for MESH4.CME 2024-02-01 08:33:24.840 | Rithmic Direct - DTC (Data) | Received security definition for symbol ESH4.CME 2024-02-01 08:33:24.840 | Rithmic Direct - DTC (Data) | Received security definition for symbol MESH4.CME 2024-02-01 08:33:28.012 | Opened cached Intraday file: D:\SierraChart\SC1\Data\ESH4.CME.scid. Thread ID: 5716 2024-02-01 08:33:28.012 | Opened cached Intraday file: D:\SierraChart\SC1\Data\MESH4.CME.scid. Thread ID: 5716 2024-02-01 08:33:40.860 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | Creating socket. Using TLS 1.2. 2024-02-01 08:33:40.861 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | New receive buffer size: 0 2024-02-01 08:33:40.861 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | Connecting to IP: 38.79.0.89. 2024-02-01 08:33:45.837 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | Socket gracefully closed by remote side. 2024-02-01 08:33:45.837 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | Socket gracefully closed by remote side. 2024-02-01 08:33:45.838 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | CloseSocket call. 2024-02-01 08:33:45.838 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | Graceful close received or receive error. Shutdown complete. Closing socket now. 2024-02-01 08:33:45.838 | HTTPS connection ID:5 to www.rithmic.com:443 for request ID:5 (3) | Closed. |
| [2024-02-01 15:56:24] |
| John - SC Support - Posts: 36286 |
|
We were wondering if you were getting our Delayed data instead of the Rithmic data. But this is not the case, you are definitely getting the data from Rithmic, therefore any delay in the data is coming from them. Refer to our policy on Rithmic data at the following link: Rithmic Trading Platform Service: Rithmic Market Data and Support Policy For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-01 16:46:47] |
| User308424 - Posts: 70 |
|
Yeah... I know the policy for Rithmic and somehow I do not wonder why it has been implemented. Last time I waited for weeks for their response... Thanks anyway, at least I know all is good from SC side. |
To post a message in this thread, you need to log in with your Sierra Chart account: