Hi everyone,
of recent my code has been producing some warnings:
Aug 20, 2012 1:17:25 PM com.dukascopy.api.impl.Indicators calculateIndicator
WARNING: There is not enough data to calculate value for MFI
and my backtests have been grinding to a halt.
When I open VisualVM the cpu time is getting used primarily by com.dukascopy.dds2.greed.agent.strategy.tester.TesterHistory.getBars().
The next process which is using a lot of cpu time is mina SocketConnectoror$Worker.run()
To the best of my knowledge all calculate indicator calls are wrapped in try catch blocks, but I cannot seem to track down where this is coming from. I am doing quite a bit of calculation on every tick using shift 0 to get the current bar value. Could the problem be somehow be coming from that (even though it doesn't seem to have given me problems in the past)?
Thanks,
MM