Support Board
Date/Time: Fri, 26 Jun 2026 09:03:54 +0000
Chartbooks or Instances
View Count: 1032
| [2025-02-01 16:38:45] |
| novaxt123 - Posts: 54 |
|
When trading, I monitor 4 different futures at the same time with the corresponding cash times. My question: What is best for optimal data processing, opening 4 individual instances or opening 4 chart books in the main instance at the same time? Thank You very much. I read the manual but it wasn't clear to me. |
| [2025-02-01 20:20:02] |
| ForgivingComputers.com - Posts: 1230 |
|
The benefits of having multiple instances are that each one can run on different cores in your CPU and you can view all chartbooks at the same time. The main drawback to using multiple instances is that more RAM is used. When 100% of memory is used, the OS must swap pages of virtual memory in and out to disk, which adds delays. With sufficient RAM you can improve performance using multiple instances.
|
| [2025-06-18 07:32:52] |
| User826383 - Posts: 11 |
|
So you are telling me to run faster, I must open more instances (chart books)? Really, my 24 cores need 24 instances? Thanks |
| [2025-06-18 08:42:58] |
| Sébastien - Posts: 153 |
|
No you don't need 24 instances for your 24 cores. Since you monitor 4 markets, you can use 4 instances or less. It depends of the workload of your 4 chartbooks. Open your Task Manager => Performance Tab, right clic on the graph => Change graph to => Logical Processors, and check on which core runs Sierra Chart (on my screenshot, it is the first one, core 0) Ideally, this core workload should not exceed 50-60% of its maximum during rest time because during high market activity (like during the NY open) it can rise 10-30%. You don't want your core to be overloaded because it can cause latency. My rule of thumb is when my core is loaded to more than 60%, it is usually time to create a new instance and to distribute the workload. When using multiple instances, there are a few drawbacks like : - If you do a Market Replay, you can't have a perfect sync between instances. - Some shortcuts like Recenter Trade DOM Scales don't work across instances. Date Time Of Last Edit: 2025-06-18 08:46:07
|
 Screenshot 2025-06-18 102822.png / V - Attached On 2025-06-18 08:43:39 UTC - Size: 123.07 KB - 238 views |
| [2026-05-21 11:57:51] |
| Xeoh85 - Posts: 9 |
|
Why haven’t you guys just implemented multi-threading at this point, to take advantage of multiple cores from one instance? How hard would it be to simply spawn a new thread per chart, for example? 8 charts, with 8 threads, running on 8 cores.
|
| [2026-05-21 13:08:47] |
| Sierra_Chart Engineering - Posts: 24120 |
|
This is very very complex, extremely complex to do it properly and safely, and often, there would be no benefit because the one thread would have to wait on another thread. Extraordinarily complex. We do plan to add a study calculation thread but still there is a lot of complexity with that, and often no benefit due to one thread having to wait for another. Once again, this is an extraordinary amount of complexity, using threads within the context of charts and certainly having a single thread per chart is out of the question. One reason, out of really hundreds of reasons, that most software, is substandard and unreliable, is improper use of threads, and there is no safety between threads. We see an incredible amount of stupidity out there with this. This is one feature that we want to add, is a study calculation thread, and it is the topmost item of the most difficult thing to implement. 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: 2026-05-21 13:10:40
|
To post a message in this thread, you need to log in with your Sierra Chart account: