Hi,
we found very important practical problem, while developing for NT8.
Description of problem:
there are many situations during the day. when we need to Cancel backtest, make some change in code, compile and run it again.
Our developers team needs to do this many times a day, during time of heavy development.
But this is not possible now - and we are forced to wait long time, until existing backtest finishes, before we can run it again. This is often between 10-30 minutes for complex strategies running on tick data. This scenario happens many times a day and the development process starts to be a real pain.
Developers in our team are more waiting until running backtest finishes than doing progress and meaningful work. Whole team is tired from this frustrating inability to Cancel backtest.
Expected behavior:
Implementation of this is not expected to be complex. Nothing is needed to store, nothing special to handle. Just basically
We need this to achieve normal development performance and quick Code-change / Compile / Run round-turn , without waiting long times until existing backtest finishes.
we found very important practical problem, while developing for NT8.
Description of problem:
there are many situations during the day. when we need to Cancel backtest, make some change in code, compile and run it again.
Our developers team needs to do this many times a day, during time of heavy development.
But this is not possible now - and we are forced to wait long time, until existing backtest finishes, before we can run it again. This is often between 10-30 minutes for complex strategies running on tick data. This scenario happens many times a day and the development process starts to be a real pain.
Developers in our team are more waiting until running backtest finishes than doing progress and meaningful work. Whole team is tired from this frustrating inability to Cancel backtest.
Expected behavior:
- We need to quickly Cancel running backtest, so we can run it again after code change.
- We don't need anything special to handle this - it is completely OK, that all previous backtest work (temporary results) can be discarded, because backtest is meant to be Run again.
Implementation of this is not expected to be complex. Nothing is needed to store, nothing special to handle. Just basically
- cancel backtest in apropriate place
- do not invoke any more callbacks,
- terminate strategy,
- cleanup internal NT8 resources to preserve its consistent state.
- Done. Users and developers are happy
We need this to achieve normal development performance and quick Code-change / Compile / Run round-turn , without waiting long times until existing backtest finishes.
Comment