NetTecture 

Yes and no - as someone currently writing a Ninja Competitor. .... I have been doing tests with a time and sales window, and I must say - the problem really is the drawing. Plus, in case of Ninja the non-wpf-approach which basically does the drawing in the single CPU thread. My WPF appraoch pretty much killed the time and sales without tricks - thanks to WPF offloading drawing to a second thread AND using the graphics card to do the rendering. But this is a lot newer. Maybe NinjaTrader 8 is a total rewrite in 3-4 years I would not bet on it

Donīt know if I understood right: Did you optimize your NT7 or are you working on your own better trading software?

aslan 

For back testing, they are able to partition each scenario, and run each in parallel with a different thread, then they collate the results and present the info back on the main thread.

And yet, the back testing function still cannot be trusted to resemble anything in real world trading. So you get faster results that are still terribly inaccurate for system building.

NT7 would only run quicker on backtesting, not in charting, even not with this "nvidia tesla" because not beeing programmed multithreading the charting - right or wrong?
GPU Engine! [AUTOLINK]Back testing[/AUTOLINK] and optimizing strategies 250 times faster! - [AUTOLINK]NinjaTrader[/AUTOLINK] Support Forum

NT7 would only run quicker on backtesting, not in charting, even not with this "nvidia tesla" because not beeing programmed multithreading the charting - right or wrong?

>>> right !

The moment that multicharts has a DOM I'm out of NT. Multicharts REALLY uses all cores.

Strangely I do not experience that type of problem. I'm running NT7 64bit on a quad-core Apple box running Windows 7 64bit. Have tons of charts with indicators open while optimizing as well as several pretty complex strategies. One tip - and you may not have tried this - it helped WONDERS on my end and it took me a year to figure that out: Comment out all your debug logs - I personally set a flag which is something you may want to do anyway. I experienced a huge speed increase and all my more fragile strategies suddenly ran rock solid. I think they may have a thread management problem that interferes with the logging - go figure.

Zoethecus: I tried to send you a private response to yours and I was unable to do so as I'm not a premiere member here (strange). My email is admin @ evilspeculator com if you want to reach me.

molecool 

Zoethecus: I tried to send you a private response to yours and I was unable to do so as I'm not a premiere member here (strange). My email is admin @ evilspeculator com if you want to reach me.

You can't PM another user until you have five posted messages, to prevent spam.

Mike

hey molecool,

sounds interesting your idea!

can you give an example of what you did / talk about ?
or show what you mean with "debug-logs" ?


that would be great !
thanks
max

resist 

Donīt know if I understood right: Did you optimize your NT7 or are you working on your own better trading software?

Both. Curreently giving NT7 a try (dont like it too much) and slowly putting some time into my own stuff.

molecool 

Strangely I do not experience that type of problem. I'm running NT7 64bit on a quad-core Apple box running Windows 7 64bit. Have tons of charts with indicators open while optimizing as well as several pretty complex strategies. One tip - and you may not have tried this - it helped WONDERS on my end and it took me a year to figure that out: Comment out all your debug logs - I personally set a flag which is something you may want to do anyway. I experienced a huge speed increase and all my more fragile strategies suddenly ran rock solid. I think they may have a thread management problem that interferes with the logging - go figure. Zoethecus: I tried to send you a private response to yours and I was unable to do so as I'm not a premiere member here (strange). My email is admin @ evilspeculator com if you want to reach me.

Could you provide a sample code piece on how you commented out the debug logs? Was that in optimise or back test?