Support Board
Date/Time: Sat, 01 Feb 2025 22:04:24 +0000
Post From: Is there common memory region that shares tick information between charts
| [2019-07-31 23:59:09] |
| |
|
does each chart communicates with SCID files and has own copy of the file Yes. Not sure the benefit of sharing the same source data since the bar time frames are generally going to be different between charts and other chart settings as well which affect bar building.In regards to disk I/O, the operating system has its own caching and with solid-state drives and being the data is read on another thread, we don't really see any practical benefit especially being that the data is read in large chunks at a time. It is not until Sierra Chart became 64-bit, did the potential for keeping the raw Intraday data in memory be possible and perhaps offer a benefit. But this is still treacherous with excessive memory use. Also the concept of disk I/O is an outdated one. With solid-state drives, especially ones directly connected to the PCI bus, and file caching, and efficient reads like Sierra Chart does, there really is not "disk I/O" that really goes on any longer. This is kind of a dated concept. During real-time chart updating, Sierra Chart does not read directly from the files, it reads from an internal cache so long as charts are updating more often than the default flush time of 3000 ms. Which we will make 5000 ms now that we are reviewing this again. 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-01 00:00:46
|