Login Page - Create Account

Support Board


Date/Time: Sun, 24 Nov 2024 22:59:38 +0000



Post From: Technical question about limitations of replay backtest spreadsheet automation

[2013-12-09 08:25:29]
Sierra Chart Engineering - Posts: 104368

Is this limitation due to computer memory/processing power?
The limitation is due to CPU speed of a core. Memory is not significant. Recent versions of Sierra Chart should perform back testing faster when doing a replay back test with tick by tick data because of caching.

We do not see how multiple cores can be used when performing a single back test. Could be used if there are multiple back tests going on.

However, then there will be synchronization issues which can be very complex to deal with. It is very easy to talk about using multiple cores, but multithreaded programming gets to be very complicated and unless it is done right, it results in an unreliable program.

It is also possible there simply is no benefit to multithreaded programming based upon the synchronization methods used. So you have to be very careful when you hear about multicore/multithreading support. It can mean unreliability unless it is done by the most best of programmers. And also if not done right it can be meaningless and of no benefit.

If you are looking for Sierra Chart to support multiple cores with back testing and make it a whole lot faster, don't wait around for that. We do not see how a single back test can be distributed across multiple cores.
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: 2013-12-09 08:28:44