The concept of drawdown as it is applied as a means of assessing risk is inherently flawed:
Source: Minimizing your risk of ruin
You really want to pursue established VAR methods for systematic risk assessment and management. Risk of ruin calcs help you capture and express your expected drawdown assuming stationarity of the trade strategy's rate of return and variance.
The concept of drawdown as it is applied as a means of assessing risk is inherently flawed:
You really want to pursue established VAR methods for systematic risk assessment and management. Risk of ruin calcs help you capture and express your expected drawdown assuming stationarity of the trade strategy's rate of return and variance.
Drawdown is a metric given by the strategy tester but that doesn't make it useful or relevant.
For example look at the max consecutive wins and max consecutive losses metrics...how relevant is that info? Are you to assume that in the future you are going to experience a successful win-rate or loss-rate comparable to that produced on historical data?
That would only happen if the future market behaves effectively identical to the past market. When has that ever been the case?
The question you need to ask yourself is what purpose are you aiming to satisfy by doing backtesting? If the answer is "I want to use past results created by the backtester as an indication of potential future results" then you have your work cut out for you.
I do backtesting as a means of debugging my code as well as a means of eliminating truly awful strategies and parameter values.
Drawdown is a metric given by the strategy tester but that doesn't make it useful or relevant.
For example look at the max consecutive wins and max consecutive losses metrics...how relevant is that info? Are you to assume that in the future you are going to experience a successful win-rate or loss-rate comparable to that produced on historical data?
That would only happen if the future market behaves effectively identical to the past market. When has that ever been the case?
The question you need to ask yourself is what purpose are you aiming to satisfy by doing backtesting? If the answer is "I want to use past results created by the backtester as an indication of potential future results" then you have your work cut out for you.
I do backtesting as a means of debugging my code as well as a means of eliminating truly awful strategies and parameter values.
If your system in backtesting is very profitable, has very small variance. but the max drawdown is above 50%, are you confindent to use it ?
If you say such a excellent system could not produce a drawdown as that high, then that means the drawdown is still correlated to the variance..........
If your system in backtesting is very profitable, has very small variance. but the max drawdown is above 50%, are you confindent to use it ?
If you say such a excellent system could not produce a drawdown as that high, then that means the drawdown is still correlated to the variance..........
Depends on what caused the drawdown. Depending on how you have engineered your trade strategy, drawdown is simply the intersection of coincidence and market timing over a historical time period.
Unless you expect future time periods to replicate these coincidences and have engineered your strategy to embark on similar market timing then future drawdown will have little to do with historical drawdown.
I don't measure drawdown in backtesting. I look for plateau's of stationarity of the market opportunities (coincidences) and my strategy's ability to take advantage of them (market timing).
I do measure the historical variance produced from these plateaus for risk of ruin assessments but that is about it.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi Pors.
How large a maximum drawdown(in percent) is generally acceptable to you? Do you have a guideline?