This is a very broad level problem, so I'm not sure what details or documentation I can provide, but I've finally found the time and have also created the necessary resources to run some rather robust and complex backtests and optimizations on nt8. The speed is certainly improved, however, when the tests get too complex (too many parameter combinations, too many instruments being tested, too many bars being tested such as 1min increments back to 2007, etc), I'm once again encountering the freezing-up of ninja. . and the 'abort' button doesn't work, because the program is just *that* frozen. I tried waiting about 20 minutes, and clicking abort the moment it un-froze for a few seconds at a time, but had no luck with this, and had to eventually use task manager to force a shut down.
Completely preventing any temporary freezing behaviors from incredibly complex or data intensive tasks may be nearly impossible, but if it could at least allow for a proper 'abort' in these cases, this would be an immense step forward. . .
Comment