Wow, this is great work! Extremely fast. Yes, this was it. Now works without a flaw.
Thanks a lot Klaus On 6 Jun., 23:22, nonlinear5 <[email protected]> wrote: > I've used the profiler and found the source for the memory leak. > Klaus, can you add this method to your BackTestDialog.java and see if > this fixes the problem? Thanks. > > public void dispose() { > btsr = null; > super.dispose(); > } > > On Jun 6, 10:07 am, nonlinear5 <[email protected]> wrote: > > > > > The backtesting mode is very demanding on memory, as it keeps the > > entire history of prices, indicators, trades, and P&L. This is so that > > the chart can be displayed after the back test. The quick way to > > reduce the demand on memory is to specify a lower resolution in the > > "bar size" parameter in the backtesting dialog. Try to set it to 5 > > minutes or even 30 minutes. Note that the results of the back test > > will be exactly the same, no matter what bar size you set. > > > Having said that, the back tester is designed to release the memory > > when a new back test starts, so it should be as fast on the first run > > as it is on the subsequent runs. If this is not so, there must be a > > memory leak somewhere. I'll take a look. -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
